On 2014-08-22 09:45-0400 Hazen Babcock wrote:
> On 8/21/2014 8:48 PM, Alan W. Irwin wrote:
>> So we were all in agreement that storage (in a file) of the SHA1 id of
>> the HEAD commits from each branch to be deleted would be enough to
>> guarantee branch resurrection, but it turns out that is inco
On 2014-08-22 12:27-0700 Alan W. Irwin wrote:
> On 2014-08-22 10:23- Arjen Markus wrote:
>
>> Hi everyone,
>> I have subscribed to the git mailing list, got a clone of the repository and
>> so should be able to do commits and see the result. I did in fact change one
>> thing and committed it
On 2014-08-22 10:23- Arjen Markus wrote:
> Hi everyone,
> I have subscribed to the git mailing list, got a clone of the repository and
> so should be able to do commits and see the result. I did in fact change one
> thing and committed it, but presumably that is just in my local copy. I gues
On 8/21/2014 8:48 PM, Alan W. Irwin wrote:
> So we were all in agreement that storage (in a file) of the SHA1 id of
> the HEAD commits from each branch to be deleted would be enough to
> guarantee branch resurrection, but it turns out that is incorrect.
> Further reading shows that git automaticall
Hi everyone,
I have subscribed to the git mailing list, got a clone of the repository and so
should be able to do commits and see the result. I did in fact change one thing
and committed it, but presumably that is just in my local copy. I guess I need
to "push" the changes to get them into the "
