From: Josef Wolf <jw@raven.inka.de>
To: git@vger.kernel.org
Subject: Re: git-svn and repository hierarchy?
Date: Fri, 6 Mar 2009 18:57:24 +0100 [thread overview]
Message-ID: <20090306175724.GB14554@raven.wolf.lan> (raw)
In-Reply-To: <eaa105840903060858g5b8f31bpb9a59d563835a9d5@mail.gmail.com>
On Fri, Mar 06, 2009 at 11:58:36AM -0500, Peter Harris wrote:
> On Fri, Mar 6, 2009 at 11:10 AM, Josef Wolf wrote:
> > On Thu, Mar 05, 2009 at 02:48:14PM -0500, Peter Harris wrote:
> >>
> >> True, but in my experience it happens considerably less often with
> >> git. I find and fix most of my typos when reviewing my change-set
> >> before doing a "git push" or "git svn dcommit".
> >
> > So you are rewriting yourself but not accept rewrites by svn ;-)
>
> No, I am not rewriting myself *after I publish*. I see the smiley, but
> I think you missed the point.
>
> "git push" or "svn ci" is the end of the rewrites.
I see. Thanks for the clarification!
> >> Indeed. Or even not-so-random names, such as cloneX/topic-name if you
> >> prefer.
> >
> > That would have the risk of multiple clones pushing to the same branch.
>
> Only if cloneX pushes to cloneY/topic-name. Does each clone not have a
> unique name?
I'd rather not rely on the clones having unique names.
> > Does that look sane?
>
> No. But it doesn't look any more insane than any other workflow
> involving Subversion that I can think of. :-)
OK, I parse that as "there's not much room for improvement" :-)
Thanks for your great help! I have learned a lot in this thread!
next prev parent reply other threads:[~2009-03-06 18:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 22:34 git-svn and repository hierarchy? Josef Wolf
2009-02-25 9:26 ` Michael J Gruber
2009-02-25 23:24 ` Josef Wolf
2009-02-26 1:02 ` Peter Harris
2009-02-27 16:58 ` Josef Wolf
2009-02-27 18:11 ` Peter Harris
2009-02-27 23:58 ` Josef Wolf
2009-02-28 2:41 ` Peter Harris
2009-02-27 17:12 ` Josef Wolf
2009-02-27 17:45 ` Michael J Gruber
2009-02-27 22:05 ` Josef Wolf
2009-02-28 17:59 ` Michael J Gruber
2009-03-03 18:51 ` Josef Wolf
2009-03-03 19:35 ` Peter Harris
2009-03-03 22:36 ` Josef Wolf
2009-03-04 0:18 ` Peter Harris
2009-03-04 19:27 ` Josef Wolf
2009-03-04 22:06 ` Peter Harris
2009-03-05 18:05 ` Josef Wolf
2009-03-05 19:48 ` Peter Harris
2009-03-06 16:10 ` Josef Wolf
2009-03-06 16:58 ` Peter Harris
2009-03-06 17:57 ` Josef Wolf [this message]
2009-03-08 20:33 ` Florian Mickler
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=20090306175724.GB14554@raven.wolf.lan \
--to=jw@raven.inka.de \
--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).