From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: unmark after committing with git.el
Date: Wed, 06 Dec 2006 13:58:06 +0100 [thread overview]
Message-ID: <el6eku$vg7$3@sea.gmane.org> (raw)
In-Reply-To: 4576BB0B.9010200@xs4all.nl
Han-Wen Nienhuys wrote:
> in the usual workflow, I mark a few files, and then commit, and then
> mark another few for commit.
>
> This patch removes the need to unmark between commits.
This should be in commit message.
>
> From ad694b33e033e3638043cd2d2970e6248beecb91 Mon Sep 17 00:00:00 2001
> From: Han-Wen Nienhuys <hanwen@xs4all.nl>
> Date: Wed, 6 Dec 2006 13:41:09 +0100
> Subject: [PATCH] git.el: unmark files in after committing.
>
>
> Signed-off-by: Han-Wen Nienhuys <hanwen@xs4all.nl>
But this break I think PCL-CVS behaviour compatibility. By the way,
[Backspace] should unmark all files.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-06 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 12:43 unmark after committing with git.el Han-Wen Nienhuys
2006-12-06 12:58 ` Jakub Narebski [this message]
2006-12-06 13:09 ` Han-Wen Nienhuys
2006-12-06 14:24 ` Alexandre Julliard
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='el6eku$vg7$3@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).