Hi,
On Wed, 3 Jan 2007, John Mandereau wrote:
> Till Rettig wrote:
>
> > Do I now understand right that when problems emerge the git pull will
> > save files under different names (or insert the problem signs, as you
> > had it) and then you have to change them and make git update-index on
>
Till Rettig wrote:
> John Mandereau wrote:
> > Please read the revised README and translate the parts of README.de that
> > brings something interesting in addition to the English README.
> >
> Well, no I checked it. I don't think there is anything I have in my own
> version. Just now when I co
John Mandereau wrote:
All translation hints other than support for a particular user should be
in English, so that all translators can share it.
Yes, that is totally true
Please read the revised README and translate the parts of README.de that
brings something interesting in addition to th
TED]>
An: Johannes Schindelin <[EMAIL PROTECTED]>
Betreff: Re: German translation help file
>
>
> > I'd rather bite the bullet and say
> >
> > $ git clone -n git://git.sv.gnu.org/lilypond.git
> > $ git checkout -b myweb web/master
> >
&
John Mandereau escreveu:
> Speaking of, isn't scripts/rev-to-commit.py supposed to update the
> committishes automagically? It would need an update to work, though.
no, rev-to-commit was a hack to transition from CVS to git.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~ha
Han-Wen Nienhuys wrote:
> John Mandereau escreveu:
> >>> git-rev-list HEAD | head -1
> >> It is way easier to say
> >>
> >> $ git rev-parse HEAD
> >
> > That's what README tells now.
>
> Actually, I think it's better to use
>
> make show-committish
>
> (which you removed from the README).
John Mandereau escreveu:
>>> git-rev-list HEAD | head -1
>> It is way easier to say
>>
>> $ git rev-parse HEAD
>
> That's what README tells now.
Actually, I think it's better to use
make show-committish
(which you removed from the README).
The SHA1 of the original is likely to be the one
Hi,
On Wed, 3 Jan 2007, John Mandereau wrote:
> Johannes Schindelin wrote:
> >
> > On Mon, 1 Jan 2007, Till Rettig wrote:
> >
> > > Es ist dabei wichtig, dass die erste Zeile das commitish enthält,
> >
> > Why would it be important that the first line has a committish?
>
> To record the revi
Johannes Schindelin wrote:
> Hi,
>
> I'll just comment the German text in English, and leave the complete
> translation to you...
>
> On Mon, 1 Jan 2007, Till Rettig wrote:
>
> > Es muss git (und evtl. cogito) installiert sein, das letztere
> > Vereinfacht die Handhabung. Weitere Informationen
Hi,
I'll just comment the German text in English, and leave the complete
translation to you...
On Mon, 1 Jan 2007, Till Rettig wrote:
> Es muss git (und evtl. cogito) installiert sein, das letztere
> Vereinfacht die Handhabung. Weitere Informationen finden sich auch noch
> im LilyPond-Wiki
>
Till Rettig wrote:
> This is now about the help file that I wrote (more or less for myself)
> to make the translation process and work with git a bit clearer. It kind
> of combines what was there about using git on this list the last weeks,
> some hints from the wiki and reference to the README
This is now about the help file that I wrote (more or less for myself)
to make the translation process and work with git a bit clearer. It kind
of combines what was there about using git on this list the last weeks,
some hints from the wiki and reference to the README file. Han-Wen
thought t
Till Rettig escreveu:
> Hello,
>
> because it caused me some difficulties to understand how the git
> conventions for commting patches worked I wrote a small helper file so
> far called README.de in the web/ directory. Could somebody check it,
> proof read it and maybe also change something if I m
Hello,
because it caused me some difficulties to understand how the git
conventions for commting patches worked I wrote a small helper file so
far called README.de in the web/ directory. Could somebody check it,
proof read it and maybe also change something if I made mistakes? I add
it in the
14 matches
Mail list logo
