Dear Sir/Madam, Here is a pdf attachment of my proposal to you. Please
read and reply I would be grateful. Peter Hans
reply to E-mail: peterh@aol.com
--
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
I would like to give a branch a "title" which is similar to the branch
description
but should be pushable.
There was a discussion several years ago with the hint to extend
push to make it shareable:
http://git.661346.n2.nabble.com/push-branch-descriptions-tt7571217.html
I've patched buildin/bran
Hi Dmitry,
On Fri, Oct 31, 2014 at 4:47 PM, Dmitry Oksenchuk wrote:
> Hi Christian,
>
>> On Thu, Oct 30, 2014 at 6:41 PM, Dmitry Oksenchuk
>> wrote:
>>>
>>> Yes, because of such amount of refs, push in "historical" repository
>>> takes 12 sec, push in "working" repository takes 0.4 sec, push in
On Wed, Oct 29, 2014 at 12:37 AM, Torsten Bögershausen wrote:
>
> On 2014-10-27 13.10, Nguyễn Thái Ngọc Duy wrote:
> []
> Nice serious, I can imagine to test & benchmark it (so I assume there is a
> branch
> on github or so ?)
It's on 'pu' now. There's a branch on my github repo, but it has some
From: Nguyễn Thái Ngọc Duy
Locked paths can be saved in a linked list so that if something wrong
happens, *.lock are removed. For relative paths, this works fine if we
keep cwd the same, which is true 99% of time except:
- update-index and read-tree hold the lock on $GIT_DIR/index really
early
5 matches
Mail list logo