måndag 20 april 2009 09:55:54 skrev Alex Blewitt <alex.blewitt@xxxxxxxxx>: > > On 20 Apr 2009, at 07:32, Robin Rosenberg wrote: > > > måndag 20 april 2009 04:40:42 skrev Alex Blewitt <alex.blewitt@xxxxxxxxx > > >: > >> On Sun, Apr 19, 2009 at 10:50 PM, Robin Rosenberg > >> <robin.rosenberg.lists@xxxxxxxxxx> wrote: > >> One advantage of attaching issues is you don't have MUA problems :-) > >> I'll try and get a patch to work via git-send-email later. > > > > The problem is review. With e-mail I can just hit reply and comment > > on your > > patch. Did your try the SMTP interface to gmail? I think e-mailing > > inlined patches is > > a nearly perfect. Inline-attachment is ok with me. That makes it > > possible to > > comment on them like any email in my mail program. > > Right, but the same approach is possible in a bug tracking system - > just comment. And people get a notification that a change has I haven't seen that. Obviously a bugtracker could cite the patch, but I don't know any that do. > apple:egit alex$ git status > # On branch master > # Your branch is ahead of 'origin/master' by 9 commits. > # > nothing to commit (working directory clean) > > apple:egit alex$ git rebase -i origin/master > Working tree is dirty > apple:egit alex$ git rebase -i d0fd6f96b9311b972c6bffa8680544607d7e3c56 > Working tree is dirty > apple:egit alex$ > > I'm probably doing something obviously wrong here, but I don't know > how to understand the difference between 'working tree is dirty' and > 'working directory clean', especially since git status (or git commit - > a) doesn't show any differences. "obviously" isn't the right word here, or status and rebase would agree on the cleanliness. If you are using bash I strong suggest you enable the nice bash prompt with some status information. It's in <gIt>/contrib/completion if you have the Git source. In a packaged version you can probably can source /etc/bash_completion. It will tell you what branch you are on and state-information, like whether a rebase is in progress or not (you would get a different message from rebase/status if that was the case). > Please excuse me whilst I figure out how to get comfortable working > with git ... It took me only ten minutes to find a bug the first time I used git :) -- robin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html