From: Tuncer Ayaz <tuncer.ayaz@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What are branches?
Date: Mon, 20 Apr 2009 00:34:05 +0200 [thread overview]
Message-ID: <4ac8254d0904191534q3abc4bdq7aebb0559803739@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0904200028340.10279@pacific.mpi-cbg.de>
On Mon, Apr 20, 2009 at 12:29 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Mon, 20 Apr 2009, Tuncer Ayaz wrote:
>
>> On Sun, Apr 19, 2009 at 5:17 PM, Johannes Schindelin
>> <Johannes.Schindelin@gmx.de> wrote:
>>
>> > if you're like me, you used Git for _way_ too long to really
>> > understand how anybody can say that Git is hard to learn. The
>> > concepts underlying Git have sunk so deep that I do not question them
>> > anymore.
>> >
>> > But it is important to keep in mind that our concept of branches is
>> > not intuitive:
>> >
>> > http://longair.net/blog/2009/04/16/git-fetch-and-merge/
>> >
>> > In particular, we have some pretty confusing nomenclature when it
>> > comes to branches, and we might want to think how to improve the
>> > situation.
>> >
>> > Food for thought on a lazy Sunday afternoon.
>>
>> Probably in the same confusion department:
>> http://blog.teksol.info/2009/04/15/beware-of-gits-content-tracking.html
>>
>> Is he right and is this the defined correct behavior?
>
> Could you please at least change the subject to something like "Something
> else, was Re: ..." when you abduct the thread?
sorry, will repost. I have to admit that I was 25% unsure whether
this is related and the right/wrong context. oh and that number is
exact :).
next prev parent reply other threads:[~2009-04-19 22:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 15:17 What are branches? Johannes Schindelin
2009-04-19 15:24 ` Michael Witten
2009-04-19 22:10 ` Tuncer Ayaz
2009-04-19 22:29 ` Johannes Schindelin
2009-04-19 22:34 ` Tuncer Ayaz [this message]
2009-04-20 11:32 ` Dmitry Potapov
2009-04-20 12:07 ` Michael J Gruber
2009-04-20 13:24 ` Dmitry Potapov
2009-04-20 13:52 ` Michael J Gruber
[not found] ` <200904201614.07735.fge@one2team.com>
2009-04-20 14:27 ` Michael J Gruber
2009-04-20 18:40 ` Dmitry Potapov
2009-04-20 20:58 ` Junio C Hamano
2009-04-20 22:08 ` Marius Vollmer
2009-04-21 0:53 ` Junio C Hamano
2009-04-21 11:41 ` Dmitry Potapov
2009-04-20 14:25 ` Johannes Schindelin
2009-04-20 16:06 ` Björn Steinbrink
2009-04-20 18:59 ` Jakub Narebski
2009-04-20 20:23 ` Björn Steinbrink
2009-04-24 13:08 ` Jakub Narebski
2009-04-24 16:29 ` Björn Steinbrink
2009-04-20 18:47 ` Dmitry Potapov
2009-04-20 19:19 ` Johannes Schindelin
2009-04-20 19:24 ` Michał Kiedrowicz
2009-04-20 20:16 ` Dmitry Potapov
2009-04-20 21:04 ` Björn Steinbrink
2009-04-20 16:13 ` Brian Gernhardt
2009-04-25 11:11 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ac8254d0904191534q3abc4bdq7aebb0559803739@mail.gmail.com \
--to=tuncer.ayaz@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).