From: Eric Wong <normalperson@yhbt.net>
To: Benoit Sigoure <tsuna@lrde.epita.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-svn: prevent dcommitting if the index is dirty.
Date: Sun, 11 Nov 2007 18:28:51 -0800 [thread overview]
Message-ID: <20071112022851.GA25675@mayonaise> (raw)
In-Reply-To: <1194806501-4796-1-git-send-email-tsuna@lrde.epita.fr>
Benoit Sigoure <tsuna@lrde.epita.fr> wrote:
> dcommit uses rebase `sync' the history with what has just been pushed to
> SVN. Trying to dcommit with a dirty index is troublesome for rebase, so now
> the user will get an error message if he attempts to dcommit with a dirty
> index.
>
> Signed-off-by: Benoit Sigoure <tsuna@lrde.epita.fr>
Thanks,
Minor nit below about indentation (which Junio can fix when applying),
but nevertheless:
Acked-by: Eric Wong <normalperson@yhbt.net>
> ---
> git-svn.perl | 3 +++
> t/t9106-git-svn-dcommit-clobber-series.sh | 6 ++++++
> 2 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/git-svn.perl b/git-svn.perl
> index dd93e32..a15df4f 100755
> --- a/git-svn.perl
> +++ b/git-svn.perl
> @@ -390,6 +390,9 @@ sub cmd_set_tree {
>
> sub cmd_dcommit {
> my $head = shift;
> + git_cmd_try { command_oneline(qw/diff-index --quiet HEAD/) }
> + 'Cannot dcommit with a dirty index. Commit your changes first'
> + . "or stash them with `git stash'.\n";
We use tabs for indentation, and spaces for alignment.
> $head ||= 'HEAD';
> my @refs;
> my ($url, $rev, $uuid, $gs) = working_head_info($head, \@refs);
--
Eric Wong
next prev parent reply other threads:[~2007-11-12 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 18:41 [PATCH] git-svn: prevent dcommitting if the index is dirty Benoit Sigoure
2007-11-12 2:28 ` Eric Wong [this message]
2007-11-12 9:11 ` Benoit Sigoure
2007-11-17 20:52 ` Eric Wong
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=20071112022851.GA25675@mayonaise \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=tsuna@lrde.epita.fr \
/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).