Re: [PATCH 1/4] Add documentation for --track and --no-track to the git-branch docs.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 1/4] Add documentation for --track and --no-track to the git-branch docs.
From: Federico Mena Quintero <federico@xxxxxxxxxx>
Date: Tue, 02 Oct 2007 18:35:20 -0500
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <1191368010.3776.198.camel@xxxxxxxxxxxxxxxxxxxxxx>

Arrrr... this should be "[PATCH 2/4]", of course.  Sorry for the
confusion.

  Federico

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- [PATCH 0/4] Make the documentation consistent for --track and --notrack
  - From: Federico Mena Quintero
- [PATCH 3/4] Mention the parameters that git-pull would need to be equivalent to a --track in the git-checkout docs
  - From: Federico Mena Quintero
- Re: [PATCH 3/4] Mention the parameters that git-pull would need to be equivalent to a --track in the git-checkout docs
  - From: Junio C Hamano
- [PATCH 0/4] Another round of the --track patches
  - From: Federico Mena Quintero
- [PATCH 1/4] Add documentation for --track and --no-track to the git-branch docs.
  - From: Federico Mena Quintero

Prev by Date: [PATCH 3/4] Note that git-branch will not automatically checkout the new branch
Next by Date: [PATCH 4/4] Make git-pull complain and give advice when there is nothing to pull from
Previous by thread: [PATCH 1/4] Add documentation for --track and --no-track to the git-branch docs.
Next by thread: [PATCH 3/4] Note that git-branch will not automatically checkout the new branch
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]