Am 07.06.2013 22:21, schrieb Constantine A. Murenin:
I'm totally fine with daily updates; but I think there still has to be
some better way of doing this than wasting 0.5s of CPU time and 5s of
HDD time (if completely cold) for each blame / log, at the price of
more storage and some pre-caching,
Am 23.05.2013 21:25, schrieb Andreas Krey:
On Thu, 23 May 2013 11:06:57 +, Andreas Krey wrote:
...
...
Don't do that, then.
Ouch, you're right. The problem is not actually in the
pull; only the *last* pull into a feature branch that
then get pushed back ff to master needs to be reversed.
Am 24.05.2013 15:42, schrieb Andreas Krey:
On Fri, 24 May 2013 11:29:00 +, Holger Hellmuth (IKS) wrote:
...
Here is an idea (probably already discussed in the long history of git):
1) the branch name is recorded in a commit (for merges the branch that
is updated)
The branch name is almost
Am 22.05.2013 17:16, schrieb Ralf Thielow:
hunk = Bereich
IMHO Kontext is better if you use a German word. Technically the context is
something else, but in a German text IMHO it fits nicer when explaining to the
user where he/she can select the n-th hunk.
Not sure if
+bare repository= bloßes Repository
Since bloßes Rep. does not convey any sensible meaning to a german
reader (at least it doesn't to me) it might as well be bare. Also bare
is used as parameter to commands
+remote tracking branch = externer Übernahmezweig
Anyone used
Am 14.05.2013 19:51, schrieb Ralf Thielow:
- repository = Projektarchiv
- bare repository = bloßes Projektarchiv
+ repository = Projektarchiv, (or just Repository?)
+ bare repository = bloßes Projektarchiv (-||-), (reines, pures Repository)
I would vote for Repository or if it needs to be
Am 15.05.2013 15:14, schrieb Jan Engelhardt:
On Wednesday 2013-05-15 14:27, Jens Lehmann wrote:
While it's spoken Packdatei, the way to actually write it is
.pack-Datei or .pack-Datei.
I actually had the '-' in there too until I tried to look up Zip-Datei
in the Duden. While I don't get the
Am 19.03.2013 12:33, schrieb Duy Nguyen:
git push . foo:bar
'.' has more like a here semantic, '..' might be a more fitting
mnemonic here.
--
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
Would it make sense to allow abbreviation similar to how git objects can
be abbreviated? This would mean origin usually could be spelled just o
--
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
Am 09.03.2013 20:28, schrieb Paul Campbell:
From 7dcd40ab8687a588b7b0c6ff914a7cfb601b6774 Mon Sep 17 00:00:00 2001
From: Herman van Rink r...@initfour.nl
Date: Tue, 27 Mar 2012 13:59:16 +0200
Subject: [PATCH 14/19] Document pull-all and push-all
---
contrib/subtree/git-subtree.txt | 8
Am 21.11.2012 01:13, schrieb Lisandro Damián Nicanor Pérez Meyer:
Well, two ideas come to my mind:
- detect when using git flow (.git/config contains [gitflow some_branch]
entries).
Shouldn't it be part of the gitflow package then?
- Show swim-lane-like graphs, including branches that may
Am 30.10.2012 09:07, schrieb Mike Norman:
Not seen any recently. I'm guessing the dev is in the path of
hurricane Sandy? (Not sarcasm, btw.)
Do you still see failures? I checked out the website just now and it
seemed to work flawlessly (at least the links I tried, could not find
any Sharing
12 matches
Mail list logo
