On Thu, Nov 14, 2013 at 08:56:07AM +0100, Thomas Rast wrote:
Whatever it was that happened to a hundred or more repos on the Jenkins
project seems to be stirring up this debate in some circles.
Making us so curious ... and then you just leave us hanging there ;-)
Any pointers to this
On Thu, Nov 14, 2013 at 05:48:50AM +0530, Sitaram Chamarty wrote:
Is there *any* way we can preserve a reflog for a deleted branch,
perhaps under logs/refs/deleted/timestamp/full/ref/name ?
I had patches to do something like this here:
On 11/14/2013 01:37 PM, Jeff King wrote:
On Thu, Nov 14, 2013 at 08:56:07AM +0100, Thomas Rast wrote:
Whatever it was that happened to a hundred or more repos on the Jenkins
project seems to be stirring up this debate in some circles.
Making us so curious ... and then you just leave us
On Thu, Nov 14, 2013 at 04:26:46PM +0530, Sitaram Chamarty wrote:
I do not know about any particular debate in git circles, but I assume
Sitaram is referring to this incident:
https://groups.google.com/d/msg/jenkinsci-dev/-myjRIPcVwU/t4nkXONp8qgJ
in which a Jenkins dev
Would be really useful anyway to have the ability to create a server-side
reference based on a SHA-1, using the Git protocol.
Alternatively, just fetching a remote repo based on a SHA-1 (not referenced by
any ref-spec but still existent) so that you can create a new reference locally
and push.
On 11/14/2013 04:39 PM, Jeff King wrote:
On Thu, Nov 14, 2013 at 04:26:46PM +0530, Sitaram Chamarty wrote:
I do not know about any particular debate in git circles, but I assume
Sitaram is referring to this incident:
https://groups.google.com/d/msg/jenkinsci-dev/-myjRIPcVwU/t4nkXONp8qgJ
On 11/14/2013 04:47 PM, Luca Milanesio wrote:
Would be really useful anyway to have the ability to create a
server-side reference based on a SHA-1, using the Git protocol.
Alternatively, just fetching a remote repo based on a SHA-1 (not
referenced by any ref-spec but still existent) so that
- Original Message -
From: Jeff King p...@peff.net
Sent: Thursday, November 14, 2013 3:14:56 AM
Subject: Re: can we prevent reflog deletion when branch is deleted?
On Thu, Nov 14, 2013 at 05:48:50AM +0530, Sitaram Chamarty wrote:
Is there *any* way we can preserve a reflog
On 11/14/2013 01:44 PM, Jeff King wrote:
On Thu, Nov 14, 2013 at 05:48:50AM +0530, Sitaram Chamarty wrote:
Is there *any* way we can preserve a reflog for a deleted branch,
perhaps under logs/refs/deleted/timestamp/full/ref/name ?
I had patches to do something like this here:
I can't resist...
On 11/14/2013 08:12 PM, Stephen Bash wrote:
[snipped some stuff from Peff]
[snipped 60 lines of python]
In honor of your last name, here's what I would do if I needed to log
ref updates (and wasn't using Gitolite):
#!/bin/bash
# -- use this as a post-receive hook
while read
[top posting, and not preserving cc's because the original email thread
below is just for context; I don't want to force people into a
discussion that they may have considered closed :-)]
Is there *any* way we can preserve a reflog for a deleted branch,
perhaps under
Sitaram Chamarty sitar...@gmail.com writes:
Whatever it was that happened to a hundred or more repos on the Jenkins
project seems to be stirring up this debate in some circles.
Making us so curious ... and then you just leave us hanging there ;-)
Any pointers to this debate?
--
Thomas Rast
On Sat, Jun 1, 2013 at 11:26 PM, Ramkumar Ramachandra
artag...@gmail.com wrote:
Sitaram Chamarty wrote:
I think I'd have to be playing with *several* branches simultaneously
before I got to the point of forgetting the branch name!
Yeah, I work on lots of small unrelated things: the
Jeff King wrote:
I wonder if simply sticking
the reflog entries into a big GRAVEYARD reflog wouldn't be a great deal
simpler and accomplish the keep deleted reflogs goal, which is what
people actually want.
Exactly what I was thinking when I read your proposal. What is the
point of having
On Sat, Jun 01, 2013 at 01:29:07PM +0530, Ramkumar Ramachandra wrote:
Jeff King wrote:
I wonder if simply sticking
the reflog entries into a big GRAVEYARD reflog wouldn't be a great deal
simpler and accomplish the keep deleted reflogs goal, which is what
people actually want.
Exactly
Jeff King wrote:
Why don't the branch names have significance? If I deleted branch foo
yesterday evening, wouldn't I want to be able to say show me foo from
2pm yesterday or even show me all logs for foo, so that I can pick the
useful bit from the list?
Oh, I misunderstood then. I didn't
On Sat, Jun 1, 2013 at 3:17 PM, Ramkumar Ramachandra artag...@gmail.com wrote:
Jeff King wrote:
Why don't the branch names have significance? If I deleted branch foo
yesterday evening, wouldn't I want to be able to say show me foo from
2pm yesterday or even show me all logs for foo, so that I
Sitaram Chamarty wrote:
I think I'd have to be playing with *several* branches simultaneously
before I got to the point of forgetting the branch name!
Yeah, I work on lots of small unrelated things: the patch-series I
send in are usually the result of few hours of work (upto a few days).
I
Hi,
Is there a way to prevent reflog deletion when the branch is deleted?
The last entry could simply be a line where the second SHA is all 0's.
--
Sitaram
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 06/01/2013 03:31 AM, Sitaram Chamarty wrote:
Is there a way to prevent reflog deletion when the branch is deleted?
The last entry could simply be a line where the second SHA is all 0's.
This is a known problem. The technical reason that this is not trivial
to solve is the possibility of a
On Sat, Jun 01, 2013 at 05:00:07AM +0200, Michael Haggerty wrote:
This is a known problem. The technical reason that this is not trivial
to solve is the possibility of a directory/file conflict between old
reflog files and references that might be created subsequently (which in
turn is a
21 matches
Mail list logo
