from #padre, various suggestions

[kevindawson]

Mithaldu:
your plugin needs rework :)
first of all, repo comes from repository, not reproduction, so a bunch of Rs need to go

secondly, staging needs to focus on patches
(optimally on staging lines)

next, commit needs to basically only be: commit, commit amend
you don't ever commit file, project or anything but the current staging area
which is modified with add and rm

checkout needs to include: branch, tag, commit id
also you'll want to have a reset command to reset the current branch marker to either branch, tag or commit id

as for log:
you need to find a way to display it as a graph
by default it should display a graph of all branches, tags, etc.; everything
see: tortoisegit
also see: github network
props for including blame

origin and upstream need to be replaced with a list of remotes
typically my cpan projects have 3-8 remotes depending on how many other people forked it

and, very important
you also need to include git fetch very prominently
as well as git push
since commit in git does not upload data, it only makes a commit

(fetch needs to be prominent because git pull is dumb and often breaks things, you basically always want to fetch, checkout branch, look at log, reset)

bowtie: well, the question is: are you happy with promoting bad practices?
what would be cool was if padre would just allow me to click a thing to the left of lines to be added to the staging area

also, it's not just about removing, it's a combination of "this needs to be better overall"

bowtie: I will add your comments here to github version issues , if thats ok with you
Mithaldu: perfectly fine

see - http://irclog.perlgeek.de/padre/2013-02-03#i_6406501

[kevindawson]

so what follows is some food for thought,

I think Mithaldu: should try the plugin in vein

[kevindawson]

next, commit needs to basically only be: commit, commit amend
you don't ever commit file, project or anything but the current staging area
which is modified with add and rm

removing menu items is do able, but educating as to why will be more fun.

[kevindawson]

as for log:
you need to find a way to display it as a graph
by default it should display a graph of all branches, tags, etc.; everything
see: tortoisegit
also see: github network
props for including blame

this is covered already

[kevindawson]

and, very important
you also need to include git fetch very prominently
as well as git push
since commit in git does not upload data, it only makes a commit

this is covered already

[kevindawson]

secondly, staging needs to focus on patches
(optimally on staging lines)

menu item Stage Patch
need more info