Am 11.11.2014 um 18:17 schrieb Junio C Hamano:
Holger Hellmuth writes:
Am 06.11.2014 um 19:45 schrieb Junio C Hamano:
This is a tangent, but I personally do not think "ticket" meshes
very well with "commit". If you already know which commit was
problematic, why are you
Am 06.11.2014 um 19:45 schrieb Junio C Hamano:
This is a tangent, but I personally do not think "ticket" meshes
very well with "commit". If you already know which commit was
problematic, why are you annotating it with a ticket before
reverting it first?
I would expect a ticket to be annotating
On 23.07.2014 21:33, Sergei Organov wrote:
What actually bothers me is the unfortunate consequence that "git pull"
is not always a no-op when nothing was changed at the origin since the
last "git pull". THIS is really surprising and probably should better be
fixed. Requiring -f is just one (obvio
Am 11.04.2014 22:20, schrieb Frank Ammeter:
#!/bin/bash
# creating a git repo "repo"
rm -rf repo
mkdir repo
cd repo
git init
# committing gitattributes with text attribute set for all files
echo "* text" > .gitattributes
git add .gitattributes
git commit -m "added .gitattributes"
# add a file wit
Am 11.04.2014 17:39, schrieb Philippe Vaucher:
FWIW, I think if you made a poll and asked which color is the most
"positive" between green and red, the vast majority of people would
say "green". Examples could be traffic green lights vs red lights, or
Coca-Cola uses red. So red is refreshing an
Am 11.04.2014 17:14, schrieb Max Horn:
More between "privacy" (or perhaps "personal safety"? think: dissident coder?) vs.
"feature that is useful to some people".
Well, at least the reason mentioned in the gmane citation about knowing
if it was 2 am for them, is strange. Did anyone ever chec
Am 11.04.2014 13:08, schrieb Michael Haggerty:
On 04/09/2014 10:50 PM, Mahmoud Asshole wrote:
[...]
Please conduct your discussions here in a civil tone. It is both more
pleasant for all involved and also more likely to elicit a response. I
hardly think that the "waste" of 12 bytes in every
Am 24.02.2014 17:21, schrieb Matthieu Moy:
$ git add foo.txt
$ git status
On branch master
Changes to be committed:
(use "git reset HEAD ..." to unstage)
modified: foo.txt
Maybe status should display a stash count if that count is > 0, as this
is part of the state of the repo.
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 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 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 22.05.2013 16:29, schrieb Kendall Shaw:
I am trying to setup a repository for use inside the LAN, but I have
been unable to checkout any branch so far. I am very new to git.
The repository is being served from gitblit over https. I have
GIT_SSL_NO_VERIFY=true. The repository was created from
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 Ge
Am 19.05.2013 18:56, schrieb Ralf Thielow:
2013/5/16 Holger Hellmuth (IKS) :
[...]
+reset = neu setzen (maybe "umsetzen"?)
"zurücksetzen"
"reset" can be used with every existing commit. "zurücksetzen"
would imply that it have to be a recent
+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 use
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
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 trans
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 http://
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 http:
Am 09.03.2013 20:28, schrieb Paul Campbell:
From 7dcd40ab8687a588b7b0c6ff914a7cfb601b6774 Mon Sep 17 00:00:00 2001
From: Herman van Rink
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 +++-
1 file chang
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 ma
Am 06.11.2012 22:07, schrieb Josef Wolf:
On Tue, Nov 06, 2012 at 08:21:25PM +, Pyeron, Jason J CTR (US) wrote:
Maybe I lost sight of your problem. Can you give a specific example of where
"it" does not work?
I guess it's _me_ who's lost. I can't figure how this is supposed to
work. Maybe
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 o
Am 15.08.2012 19:30, schrieb Junio C Hamano:
The current rule is very
simple and understandable. You either say from the command line
exactly what should happen (refspec without colon is the same as the
refspec with colon at the end, meaning "do not track"; if you want
to track, you write what t
Am 15.07.2012 00:24, schrieb Zeeshan Ali (Khattak):
On Sun, Jul 15, 2012 at 12:26 AM, Junio C Hamano wrote:
"Zeeshan Ali (Khattak)" writes:
What about '^' and '^^' that I suggested?
If you want a shortcut, you might try this:
echo "ref: HEAD" > .git/h
Then you can use 'h' instead of 'HEA
Am 08.07.2012 17:43, schrieb pbGit:
Just tried starting again on my local machine because when I tried pushing,
git said that it local was also set to bare init. When I looked this was
the case. Silly me.
So I deleted on my local and added a single file and when I try pushing this
I get the fo
Am 08.07.2012 11:12, schrieb pbGit:
http://www.petermac.com/setup-git-local-and-remote-repositories/ this . All
The recipe at this address seems to have a "--bare" parameter missing at
the git init in step 7
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a
27 matches
Mail list logo
