git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vitor Antunes <vitor.hda@gmail.com>
To: Thomas Berg <merlin66b@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-p4: Corrected typo.
Date: Mon, 31 Jan 2011 11:25:30 +0000	[thread overview]
Message-ID: <AANLkTinCL6+oTAbh4WpsWHx8cZ8cxZvQxSO9EX_xsHh0@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=kmcWn9WWbhA4bMZ5bEo1imacEugT0BcOU9jry@mail.gmail.com>

Hi Thomas,

On Sun, Jan 30, 2011 at 11:34 PM, Thomas Berg <merlin66b@gmail.com> wrote:
> By the way, on this mailing list please don't top post. I think the
> preferred style is interleaved posting:
> http://en.wikipedia.org/wiki/Posting_style#Interleaved_style

Thanks for introducing me to these "rules" that are being used within
the git community :)

>> I also have some branch detection related patch prepared. Do you use
>> this feature often?
>
> No, the Perforce repo I work with is so non-standard that the only
> solution has been to import all the branches separately and graft the
> history together. This covers all my needs at the moment.

Maybe I'm not seeing some obvious limitation, but I can't imagine a
branching structure that can't be imported into git. Could please you
give me an example?

Thanks,

-- 
Vitor Antunes

  reply	other threads:[~2011-01-31 11:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19  1:38 [PATCH 0/2] git-p4: Rename and copy detection improvements Vitor Antunes
2010-11-19  1:38 ` [PATCH 1/2] git-p4: Don't edit renamed files if not necessary Vitor Antunes
2010-11-19 12:14   ` Vitor Antunes
2010-11-25  1:26   ` [PATCH] git-p4: Corrected typo Vitor Antunes
2011-01-27 23:35     ` Vitor Antunes
2011-01-28 15:19       ` Thomas Berg
2011-01-29  2:41         ` Vitor Antunes
2011-01-30 23:21           ` Vitor Antunes
2011-01-30 23:34             ` Thomas Berg
2011-01-31 11:25               ` Vitor Antunes [this message]
2011-01-31 12:51                 ` Thomas Berg
2011-01-31 13:39                   ` Vitor Antunes
2011-01-31 15:54                     ` Vitor Antunes
2011-02-04  8:59                       ` Thomas Berg
2010-11-19  1:38 ` [PATCH 2/2] git-p4: Added copy detection support Vitor Antunes

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=AANLkTinCL6+oTAbh4WpsWHx8cZ8cxZvQxSO9EX_xsHh0@mail.gmail.com \
    --to=vitor.hda@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=merlin66b@gmail.com \
    /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).