From: Junio C Hamano <gitster@pobox.com>
To: Alexandre Bourget <alexandre.bourget@savoirfairelinux.com>
Cc: Git Mailing List <git@vger.kernel.org>, paulus@samba.org
Subject: Re: [PATCH] Mod. gitk to support REBASE (with stash support).
Date: Wed, 08 Aug 2007 12:53:20 -0700 [thread overview]
Message-ID: <7vvebp3irz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1186598028457-git-send-email-alexandre.bourget@savoirfairelinux.com> (Alexandre Bourget's message of "Wed, 8 Aug 2007 14:33:48 -0400")
Alexandre Bourget <alexandre.bourget@savoirfairelinux.com>
writes:
> ---
> Adds a context menu for commits, so that a 'rebase' can be done.
>
> Optionally, it will ask if you want to 'stash' current work before doing so.
>
> TODO: better error handling.
Please do not discard a commit log message by placing them after
the three-dashes. A good commit message would be of this form:
- A single line to summarize what it does (goes to Subject);
- A blank line (paragraph break);
- A paragraph or more that elaborate on the above summary, if
needed, and defend why the change is a good idea; especially
if you considered other alternatives, a comparison to justify
your choice.
This is largely up to Paulus, but I think anything that
updates the repository should go to git-gui, not gitk. The
latter is primarily a viewer.
prev parent reply other threads:[~2007-08-08 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 18:33 [PATCH] Mod. gitk to support REBASE (with stash support) Alexandre Bourget
2007-08-08 19:31 ` Peter Baumann
2007-08-08 19:42 ` Johannes Schindelin
2007-08-08 20:08 ` David Kastrup
2007-08-09 3:26 ` Shawn O. Pearce
2007-08-09 5:51 ` David Kastrup
2007-08-09 6:58 ` Shawn O. Pearce
2007-08-09 7:21 ` Shawn O. Pearce
2007-08-09 7:55 ` David Kastrup
2007-08-08 19:53 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vvebp3irz.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=alexandre.bourget@savoirfairelinux.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox