On 05/15/2014 12:06 PM, Philip Oakley wrote:
> From: "John Fisher"
>> I assert based on one piece of evidence ( a post from a facebook dev)
>> that I now have the worlds biggest and slowest git
>> repository, and I am not a happy guy. I used to have the worlds
>> biggest CVS repository, but CVS ca
On 08/01/2014 10:48 AM, Mike Stump wrote:
>> There is also git-imerge, third party tool that is intended to help
>> merging changes (and make it possible to do it in incremental way).
> Then remove git merge and replace it with git-imerge. :-) Anyway, I read
> that, and I can see some beauty of
On 10/11/2013 06:07 AM, Yoshioka Tsuneo wrote:
> + prefix_len = ((prefix_len >= 0) ? prefix_len :
> 0);
> + strncpy(pre_arrow, arrow - prefix_len,
> prefix_len);
> + pre_arrow[prefix_len] = '¥0';
This seems to b
On 03/02/2015 10:12 AM, Joey Hess wrote:
I support this proposal, as someone who no longer releases tarballs
of my software, when I can possibly avoid it. I have worried about
signed tags / commits only being a SHA1 break away from useless.
As to the implementation, checksumming the collection o
On 03/02/2015 12:08 PM, Junio C Hamano wrote:
I have a
hazy recollection of what it would take to replace SHA-1 in git with
something else; it should be possible (though tricky) to do it lazily,
where a tree entry has bits (eg, some of the currently unused file
mode bits) to denotes which hash al
On 04/20/2015 09:41 AM, FusionX86 wrote:
Hopefully this is an appropriate place to ask questions about git-p4.
I started at a company that wants to migrate from Perforce to Git. I'm
new to Perforce and have been trying to learn just enough about it to
get through this migration.
You might also
On 08/11/2012 10:14 AM, Steven Walter wrote:
This fixes a bug where git finds the incorrect merge parent. Consider a
repository with trunk, branch1 of trunk, and branch2 of branch1.
Without this change, git interprets a merge of branch2 into trunk as a
merge of branch1 into trunk.
Signed-off-by
On 08/11/2012 10:14 AM, Steven Walter wrote:
Consider the case where you have trunk, branchA of trunk, and branchB of
branchA. trunk is merged back into branchB, and then branchB is
reintegrated into trunk. The merge of branchB into trunk will have
svn:mergeinfo property references to both bran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/18/2012 01:43 PM, Steven Walter wrote:
> How about a Signed-Off-By?
Signed-Off-By: Sam Vilain
Sam
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCgAGBQJQMCcnAAoJEBdtaL3wGtIoJ1UIAIJ6Xz5OEMmMk1tq546eggHg
I+sJIF
9 matches
Mail list logo