[darcs-users] rebase feedback and amend-record flexibility

[Florent Becker]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 03/04/2012 11:18, Gabriel Kerneis a écrit :
> On Mon, Apr 02, 2012 at 04:29:05PM -0600, Michael Hendricks wrote:
>>> I'd say that even the existing version of amend-record would be
>>> improved by issuing a warning (with a request for confirmation)
>>> if I change a patch that is also present in the default-repo.
>>> 
>>> "Warning: This operation modifies a patch the exists in the
>>> default remote repo. Are you sure? [yN]"
>>> 
>> 
>> I agree.
> 
> I see the point, but it means that you wouldn't be able to
> amend-record without access to remote repo.  No thanks, there is a
> reason why I use darcs rather than svn…
> 
A way to implement that would be to have a "public" or "private"
status in each repository. Public repositories always warn you before
amending. Private repositories would warn you about patches you haved
pulled-from/sent-to/pushed-to a public repository. This alone works as
long as you don't pull from a private repo to a public one (you always
push). For that last case, you want to be able to mark patch as
published in the private repo (darcs publish or something), and warn
when you pull an unpublished patch (maybe only if you're pulling into
a public repo).

Florent
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk969d4ACgkQTCPcDztjGo5fywCcCTdo1V+E7Q4ACuIVcXyADFe+
nrMAn0heeRZEk93RIos6SrlDPEYt2b6R
=Vq9K
-----END PGP SIGNATURE-----