All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steve Frécinaux" <nudrema@gmail.com>
To: git@vger.kernel.org
Subject: [RFC] git-svn: make git-svn commit-diff able to work without explicit arguments
Date: Tue, 02 Jan 2007 19:23:26 +0100	[thread overview]
Message-ID: <459AA31E.5070705@gmail.com> (raw)

Hello,

When using git-svn to access a SVN repo, the commit policy may vary. 
While git makes you commit small patches often, svn users tend to prefer 
bigger patches that implement a functionnality at once.

So at the end you have a SVN commit which corresponds to several git ones.

What you can do in this case is :

   git-svn commit-diff --edit -r$REV remotes/git-svn HEAD

Which effect is that it commits (at once) all the commits between the 
latest svn fetch and HEAD.

What I'm proposing here is this:

  - use the latest fetched rev the default for the -r argument.
  - use remotes/git-svn and HEAD the defaults for the treeish objects.

A smarter way to take these defaults would be to take the last revision 
in the current branch (which can be something else than git-svn if it 
wasn't rebased/merged recently) and the relevant commit in the current 
branch.

Additionnaly, --edit could be enabled by default if -m is not set and it 
is used interactively, eventually using an option in repo-config.

Any comment ?

             reply	other threads:[~2007-01-02 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 18:23 Steve Frécinaux [this message]
2007-01-02 18:40 ` [RFC] Re: git-svn: make git-svn commit-diff able to work without explicit arguments Pierre Habouzit
2007-01-02 19:18 ` [RFC] " Eric Wong
2007-01-02 20:30 ` Junio C Hamano
2007-01-02 21:13   ` [RFC] " Pierre Habouzit
2007-01-02 21:26     ` Brian Gernhardt
2007-01-02 21:58       ` Jakub Narebski
2007-01-02 22:27         ` Pierre Habouzit
2007-01-02 22:01     ` Junio C Hamano
2007-01-02 23:09     ` Steve Frécinaux

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=459AA31E.5070705@gmail.com \
    --to=nudrema@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.