[PATCH] bookmarks: allow pushkey if new equals current

Augie Fackler raf at durin42.com
Tue Aug 26 15:06:24 CDT 2014


On Aug 26, 2014, at 4:05 PM, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:

> 
> 
> On 08/26/2014 09:05 PM, Augie Fackler wrote:
>> On Tue, Aug 26, 2014 at 06:56:15AM -0700, Durham Goode wrote:
>>> # HG changeset patch
>>> # User Durham Goode <durham at fb.com>
>>> # Date 1409054321 25200
>>> #      Tue Aug 26 04:58:41 2014 -0700
>>> # Node ID c27758084fdb17115211958666f3184282291143
>>> # Parent  7eef5a87ce3ff761711c69526bf422fdc2dc696d
>>> bookmarks: allow pushkey if new equals current
>> 
>> Seems reasonable. Queued.
> 
> Does not seems that reasonable to me. Can we discuss it at the sprint?

Why not elaborate here? Basically, if you're making a request and the end state of your request is already the current state, I don't really see a reason to reject the push. Can you think of something?

> 
> -- 
> Pierre-Yves David

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20140826/736b02ac/attachment.pgp>


More information about the Mercurial-devel mailing list