GNU bug report logs - #49570
28.0.50; url-http proxy connection-wait

Previous Next

Package: emacs;

Reported by: Madhu <enometh <at> meer.net>

Date: Thu, 15 Jul 2021 10:18:02 UTC

Severity: normal

Tags: patch

Found in version 28.0.50

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #51 received at 49570 <at> debbugs.gnu.org (full text, mbox):

From: Gregory Heytings <gregory <at> heytings.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "Basil L. Contovounesios" <contovob <at> tcd.ie>, enometh <at> meer.net,
 49570 <at> debbugs.gnu.org, larsi <at> gnus.org, akrl <at> sdf.org
Subject: Re: bug#49570: 28.0.50; url-http proxy connection-wait
Date: Thu, 22 Jul 2021 07:30:30 +0000
>> If pruning loses data it shouldn't be enabled by default in all 
>> checkouts, e.g. if a branch is accidentally deleted by someone else 
>> then simply fetching shouldn't propagate that deletion for others.
>
> Of course.  Don't worry, we won't do that.
>

Why on earth won't you do that?  Deleting a branch (or removing a tag) 
does *not* lose any data / commit, it only removes a pointer / label to a 
particular commit.  For example anyone can still access the commits of the 
feature/native-comp branch with git checkout fa65c044f2.  Should someone 
accidentally delete a branch, it is easy to create it again.

Setting this config variable is much better than telling people to say 
"git remote prune origin" from time to time as you suggested, it does the 
same, except that it happens automatically.




This bug report was last modified 4 years and 2 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.