Which version is the new one? 1.6.2.x? Because I have a 1.6.0.x and it
doesn't allow me to skip the -b and the local branch name.
Cheers,
El ds 18 de 04 de 2009 a les 00:07 +0100, en/na Simos Xenitellis va
escriure:
On Fri, Apr 17, 2009 at 10:41 PM, Jason D. Clinton m...@jasonclinton.com
Hi,
I have some questions/doubts/things I can't understand quite well right
now with git and how to use branches.
I was trying to commit+push a new Italian translation for gtk+ 2-16
branch, since looks like it has one string left:
http://l10n.gnome.org/vertimus/gtk+/gtk-2-16/po/it
I switched
2009/4/18 Milo Casagrande m...@casagrande.name:
Hi,
I have some questions/doubts/things I can't understand quite well right
now with git and how to use branches.
I was trying to commit+push a new Italian translation for gtk+ 2-16
branch, since looks like it has one string left:
On Sat, Apr 18, 2009 at 04:24:18PM +0200, Milo Casagrande wrote:
Hi,
I have some questions/doubts/things I can't understand quite well right
now with git and how to use branches.
I was trying to commit+push a new Italian translation for gtk+ 2-16
branch, since looks like it has one string
Hi,
Il giorno sab, 18/04/2009 alle 16.08 +0100, Simos Xenitellis ha scritto:
If there is an existing it.po in the repository, it is not required to
'git add'.
Hmmm... my 'git help add' says I have to do it even if I modify one
file.
If I try to 'git commit' without 'git add' before, it
Hi!
Il giorno sab, 18/04/2009 alle 16.08 +0100, Simos Xenitellis ha scritto:
If there is an existing it.po in the repository, it is not required to
'git add'.
Hmmm... my 'git help add' says I have to do it even if I modify one
file.
If I try to 'git commit' without 'git add'
On Sat, Apr 18, 2009 at 4:43 PM, Johannes Schmid j...@jsschmid.de wrote:
Hi!
Il giorno sab, 18/04/2009 alle 16.08 +0100, Simos Xenitellis ha scritto:
If there is an existing it.po in the repository, it is not required to
'git add'.
Hmmm... my 'git help add' says I have to do it even if
2009/4/18 Simos Xenitellis simos.li...@googlemail.com:
On Sat, Apr 18, 2009 at 4:43 PM, Johannes Schmid j...@jsschmid.de wrote:
C. Just use 'git commit LL.po' so that we specify which file we want
to add and commit, in one line.
We do not need to 'git add' the modified files, just use when we
Hi all!
I tried to follow the Git translators guide[1] to update the anjuta
translation (which is already branched).
So I git clone it and then I tried to switch to the gnome-2-26 branch
but failed with the git checkout --track origin/gnome-2-26 command.
After some research I finally found
On Fri, Apr 17, 2009 at 12:59 PM, Gil Forcada gforc...@gnome.org wrote:
Hi all!
I tried to follow the Git translators guide[1] to update the anjuta
translation (which is already branched).
So I git clone it and then I tried to switch to the gnome-2-26 branch
but failed with the git checkout
I hope so too, but my small research ended up with this that at least
works by now :)
Cheers,
El dv 17 de 04 de 2009 a les 14:23 +0200, en/na Luca Ferretti va
escriure:
2009/4/17 Gil Forcada gforc...@gnome.org:
Should I update the working with branches section with this commands?
I
On Fri, Apr 17, 2009 at 1:23 PM, Luca Ferretti elle@libero.it wrote:
2009/4/17 Gil Forcada gforc...@gnome.org:
Should I update the working with branches section with this commands?
I hope there is a more simple way to do this. This seems a nonsense to
me: create a new local branch in
Simos Xenitellis ha scritto:
We have mentioned these some time ago. Search for 'shallow' clones.
It's the '--depth' parameter in 'git clone'.
My personal view is that a shallow clone (that is, a clone with limited history)
provides small gains. More comments and benchmarking on this would be
2009/4/17 Luca Ferretti elle@libero.it:
2009/4/17 Gil Forcada gforc...@gnome.org:
Should I update the working with branches section with this commands?
I hope there is a more simple way to do this. This seems a nonsense to
me: create a new local branch in order to commit+push on an
Simos Xenitellis ha scritto:
In practice the space difference is not significant. We should be able to have
real statistics on this soon, so that we can have a proper guideline on
shallow clones.
That would be interesting, at least to have an idea of what to expect.
AFAIK, the standing
On Fri, Apr 17, 2009 at 3:51 PM, Milo Casagrande m...@casagrande.name wrote:
Simos Xenitellis ha scritto:
In practice the space difference is not significant. We should be able to
have
real statistics on this soon, so that we can have a proper guideline on
shallow clones.
That would be
2009/4/17 Kalle Vahlman kalle.vahl...@gmail.com:
2009/4/17 Luca Ferretti elle@libero.it:
I hope there is a more simple way to do this. This seems a nonsense to
me: create a new local branch in order to commit+push on an existing
branch on server...
Uh, so assuming this comment is in
On Fri, Apr 17, 2009 at 8:55 PM, Luca Ferretti elle@libero.it wrote:
2009/4/17 Kalle Vahlman kalle.vahl...@gmail.com:
2009/4/17 Luca Ferretti elle@libero.it:
I hope there is a more simple way to do this. This seems a nonsense to
me: create a new local branch in order to commit+push on
On Fri, Apr 17, 2009 at 3:09 PM, Simos Xenitellis
simos.li...@googlemail.com wrote:
I suppose there must be some story behind the question 'Why do we specify
the branch name instead of reusing the remote branch name by default?
It feels somewhat weird.'.
With a big more experience we should
On Fri, Apr 17, 2009 at 10:21 PM, Jason D. Clinton m...@jasonclinton.com
wrote:
On Fri, Apr 17, 2009 at 3:09 PM, Simos Xenitellis
simos.li...@googlemail.com wrote:
I suppose there must be some story behind the question 'Why do we specify
the branch name instead of reusing the remote branch
On Fri, Apr 17, 2009 at 4:29 PM, Simos Xenitellis
simos.li...@googlemail.com wrote:
Is the '--track' parameter required when using 'git checkout'?
My git-config manpage says its on by default and it has been that way
for as long as I've been using git.
On 4/17/09, Simos Xenitellis simos.li...@googlemail.com wrote:
[...]
There Accounts team is understaffed and several requests take long to
be fulfilled.
In general, only those with missing/erroneous/incorrectly filled in
data. Or requests regarding teams with coordinators that forgot their
On Fri, Apr 17, 2009 at 11:28 PM, Christian Rose ment...@gnome.org wrote:
On 4/17/09, Simos Xenitellis simos.li...@googlemail.com wrote:
[...]
There Accounts team is understaffed and several requests take long to
be fulfilled.
In general, only those with missing/erroneous/incorrectly
On Fri, Apr 17, 2009 at 10:41 PM, Jason D. Clinton m...@jasonclinton.com
wrote:
On Fri, Apr 17, 2009 at 4:29 PM, Simos Xenitellis
simos.li...@googlemail.com wrote:
Is the '--track' parameter required when using 'git checkout'?
My git-config manpage says its on by default and it has been that
24 matches
Mail list logo
