> -----Original Messages-----
> From: "Daniel Shahaf" <d.s_at_daniel.shahaf.name>
> Sent Time: 2019-12-17 09:29:22 (Tuesday)
> To: wuzhouhui <wuzhouhui14_at_mails.ucas.ac.cn>
> Cc: subversion <users_at_subversion.apache.org>
> Subject: Re: quilt-like feature, to support patch series
>
> wuzhouhui wrote on Mon, 16 Dec 2019 06:57 +00:00:
> > I don't want to commit changes until I think the changes are good enough. After
> > all, commit to a branch is also a commit.
>
> There is no technical requirement that commits to branches be as stable
> as commits to trunk; that's purely a social construct and, as such,
> subject to change. For example, in Subversion's own development we
> explicitly encourage not-necessarily-fully-baked commits, but ask that
> they be clearly labeled in the log message; see
> https://subversion.apache.org/docs/community-guide/conventions.html#log-messages
> (last three paragraphs only). Or you could make the distinction based on the
> branch's URL, etc..
>
> > > You could also use git-svn(1) local branches, for example. Or you could use
> > > quilt on top of Subversion.
> >
> > Using quilt on top of Subversion seems is a good idea.
>
> To do this, I guess you'll want to write a script that automatically
> commits a patch series along with log messages (from `quilt header -e`)?
> If you do, please consider publishing it; it's not the first time this
> question has come up so it'll probably be useful to others.
I'm going to hack Subversion, instead of quilt.
>
> Cheers,
>
> Daniel
Received on 2019-12-17 05:38:43 CET