On Nov 24, 2:20 pm, Roddie Grant wrote:
[...]
>> To make things simpler to grok, you can think of all those three types
>> of objects as being plain text files.
>> Playing with `git ls-tree` and `git cat-file` can give a very clear
>> idea about how objects reference one another.
> Thanks Konstan
On Fri, Dec 10, 2010 at 3:46 AM, Konstantin Khomoutov
wrote:
> On Nov 24, 2:20 pm, Roddie Grant wrote:
>
> [...]
>>> To make things simpler to grok, you can think of all those three types
>>> of objects as being plain text files.
>>> Playing with `git ls-tree` and `git cat-file` can give a very c
Hello,
Hello,
I have a git repository, I commited by diferent accounts just that
same people. How merge historic into logs?
Thanks in advance.
--
Marcello Henrique
Blog - http://faraohh.wordpress.com
Associação Software Livre de Goiás (www.aslgo.org.br)
Cercomp - UFG (www.cercomp.ufg.br)
--
Y
Rick DeNatale wrote:
[...]
>> I've spotted one minor deficiency in the article so far (there's no
>> such thing as the "HEAD of the current branch" as Git maintains just
>> one HEAD ref)
> Not exactly.
>
> .git/HEAD contains an indirect reference to a git ref so, if I'm
> working on the branch foo
Marcello Henrique wrote:
> I have a git repository, I commited by diferent accounts just that
> same people. How merge historic into logs?
I can't quite parse this.
Do you mean you have a line (or lines) of commits made by different
committers which are, in fact, the same person, and now you wan
steve.maring wrote:
[...]
> $ git svn clone -s http://192.168.1.10/svn/project project
>
> that will checkout http://192.168.1.10/svn/project/trunk to project
>
> now, I go over to my shared folder space and make a git repo ...
[...]
> and then, the interesting thing to note is that over in /home/
Hi,
The first option, commits made by different committers which are, in
fact, the same person.
On Fri, Dec 10, 2010 at 14:21, Konstantin Khomoutov wrote:
> Marcello Henrique wrote:
>
>> I have a git repository, I commited by diferent accounts just that
>> same people. How merge historic into lo
Marcello Henrique wrote:
> The first option, commits made by different committers which are, in
> fact, the same person.
Then you should probably use a properly instrumented call to
`git filter-branch --commit-filter`
According to the git-filter-branch manual [1], it exports a set of
environment va
Hi Konstantin,
Exactly what I needed, I'll read the manual reference that you indicated.
Thanks very much.
On Fri, Dec 10, 2010 at 15:34, Konstantin Khomoutov wrote:
> Marcello Henrique wrote:
>> The first option, commits made by different committers which are, in
>> fact, the same person.
> Th
On Dec 10, 1:46 pm, Konstantin Khomoutov wrote:
> I recently came across this paper [1] which you may find useful as it
> tries to explain Git on the object level, showing the precise steps
> Git performs to create a new commit.
>
> [...]
> 1.http://www.newartisans.com/2008/04/git-from-the-botto
On Fri, Dec 10, 2010 at 11:14 AM, Konstantin Khomoutov
wrote:
> The idea is that the "HEAD" is a distinguished reference, which is
> used to point to the commit object on which the work tree is based,
> and it has no inherent relation to the notion of the "current branch".
Actually .git/HEAD is e
11 matches
Mail list logo
