On Fri, Mar 7, 2014 at 9:47 PM, Nguyễn Thái Ngọc Duy pclo...@gmail.com wrote:
The diff against v4 is kinda big but it's mostly about converting
`...` to $(...) and making git_path() and friends return a const
string.
Another notable change is I no longer attempt to support checkouts on
On Fri, Mar 7, 2014 at 9:47 PM, Nguyễn Thái Ngọc Duy pclo...@gmail.com wrote:
We allow the user to relocate certain paths out of $GIT_DIR via
environment variables, e.g. GIT_OBJECT_DIRECTORY, GIT_INDEX_FILE and
GIT_GRAFT_FILE. Callers are not supposed to use git_path() or
git_pathdup() to get
On Fri, Mar 7, 2014 at 9:48 PM, Nguyễn Thái Ngọc Duy pclo...@gmail.com wrote:
(alias R=$GIT_COMMON_DIR/repos/id)
- linked checkouts are supposed to keep its location in $R/gitdir up
to date. The use case is auto fixup after a manual checkout move.
- linked checkouts are supposed to
On Fri, Mar 7, 2014 at 9:48 PM, Nguyễn Thái Ngọc Duy pclo...@gmail.com wrote:
In linked checkouts, borrowed parts like config is taken from
$GIT_COMMON_DIR. $GIT_DIR/config is never used. Report them as
garbage.
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
diff --git a/path.c
Hey Eric,
Its been nice learning from you about how to submit patches to git.
was a nice learning curve, now I'm looking into the ideas and will contact the
appropriate mentor soon with a plan.
Thanks
- Karthik
On Sun, Mar 9, 2014 at 1:19 PM, Eric Sunshine sunsh...@sunshineco.com wrote:
On
On Sun, Mar 9, 2014 at 3:21 PM, Eric Sunshine sunsh...@sunshineco.com wrote:
On Fri, Mar 7, 2014 at 9:48 PM, Nguyễn Thái Ngọc Duy pclo...@gmail.com
wrote:
In linked checkouts, borrowed parts like config is taken from
$GIT_COMMON_DIR. $GIT_DIR/config is never used. Report them as
garbage.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07.03.2014 22:04, Jeff King wrote:
Yes, this is a well-known issue. The only safe operation on a
repository for which somebody else controls hooks and config is to
fetch from it (upload-pack on the remote repository does not
respect any
On 03/09/2014 07:46 AM, Torsten Bögershausen wrote:
After creating a local repository with these two branches, and a server
repository with git init --bare, and pushing the two branches:
git remote add originfoo@bar:~/path/test.git
git push origin master-g
git push origin master-x
HEAD on the remote repo is indeed used to determine what to check out
when cloning. It's quite normal to change it to anything you like. To
change it, you usually use git symbolic-ref HEAD master-x instead of
directly editing that file.
On Sun, Mar 9, 2014 at 8:54 PM, Carlos Pereira
On 3/9/2014 12:54 PM, Carlos Pereira wrote:
On 03/09/2014 07:46 AM, Torsten Bögershausen wrote:
After creating a local repository with these two branches, and a
server repository with git init --bare, and pushing the two branches:
git remote add originfoo@bar:~/path/test.git
git push
On Mar 7, 2014, at 7:50 PM, Henri GEIST wrote:
Le vendredi 07 mars 2014 à 15:37 -0800, Junio C Hamano a écrit :
Henri GEIST geist.he...@laposte.net writes:
This information is technical in nature but has some importance for general
users.
As this kind of clone have a separate gitdir, you
There is a git remote set-head to manipulate HEAD in a remote
repository.
Thanks, that is useful (like git symbolic-ref HEAD master-x suggested by
Kevin, much better than editing the text file)
I agree that this might be viewed as a user experience issue.
But I can not come up with a possible
Simplify if chain in install_branch_config().
Signed-off-by: Adam a...@sigterm.info
---
branch.c | 46 +++---
1 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/branch.c b/branch.c
index 723a36b..b2d59f1 100644
--- a/branch.c
+++ b/branch.c
On 3/4/2014 11:22 AM, Junio C Hamano wrote:
Ilya Bobyr ilya.bo...@gmail.com writes:
Built-in commands can specify names for option arguments, that are shown
when usage text is generated for the command. sh based commands should
be able to do the same.
Option argument name hint is any text
Built-in commands can specify names for option arguments when usage text
is generated for a command. sh based commands should be able to do the
same.
Option argument name hint is any text that comes after [*=?!] after the
argument name up to the first whitespace. Underscores are replaced with
15 matches
Mail list logo
