git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 8/8] Use the early config machinery to expand aliases

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 13, 2017, 11:25 UTC
Message-ID
<alpine.DEB.2.21.1.1706131323330.171564@virtualbox>
In-Reply-To
<20170610100730.j62kh2hayt6zknr5@sigill.intra.peff.net>
Hi Peff,
On Sat, 10 Jun 2017, Jeff King wrote:
Show 31 quoted lines
> On Thu, Jun 08, 2017 at 09:53:53PM +0200, Johannes Schindelin wrote:
> 
> > @@ -245,36 +201,37 @@ static int handle_options(const char ***argv, int *argc, int *envchanged)
> >  
> >  static int handle_alias(int *argcp, const char ***argv)
> >  {
> > +	struct strbuf cdup_dir = STRBUF_INIT;
> >  	int envchanged = 0, ret = 0, saved_errno = errno;
> >  	int count, option_count;
> >  	const char **new_argv;
> >  	const char *alias_command;
> >  	char *alias_string;
> > -	int unused_nongit;
> > -
> > -	save_env_before_alias();
> > -	setup_git_directory_gently(&unused_nongit);
> >  
> >  	alias_command = (*argv)[0];
> > -	alias_string = alias_lookup(alias_command, NULL);
> > +	alias_string = alias_lookup(alias_command, &cdup_dir);
> >  	if (alias_string) {
> >  		if (alias_string[0] == '!') {
> >  			struct child_process child = CHILD_PROCESS_INIT;
> >  
> > +			if (cdup_dir.len)
> > +				setup_git_directory();
> > +
> 
> I'm really confused here. We went to all the trouble to record the
> cdup_dir as part of the alias lookup so that we could make sure to
> chdir() to it.
Right, that was my first idea.

But then the test suite taught me that we set at least GIT_PREFIX and that tests break (or, in other words, promises Git made earlier) if those variables are not set.

So as a quick fix, I simply called setup_git_directory() instead of chdir(cdup_dir.buf).

> I understand why you must use setup_git_directory() and not just a
> chdir(), because the latter sets up variables like GIT_PREFIX and
> GIT_DIR that the shell alias may be depending on.
Exactly.
> But couldn't we just unconditionally do:
> 
>   setup_git_directory_gently();
But of course we can do that! Why on earth did I not think of that...
Will change the code accordingly.

Ciao, Dscho

Previous: Junio C HamanoNext: Jeff King
Message 21 of 32 in “Avoid problem where git_dir is set after alias expansion”
  1. 0/8 Avoid problem where git_dir is set after alias expansionJohannes Schindelin, Jun 8, 2017
  2. 2/8 config: report correct line number upon errorJohannes Schindelin, Jun 8, 2017
  3. Jeff KingJun 10, 2017
  4. Johannes SchindelinJun 13, 2017
  5. Jeff KingJun 13, 2017
  6. 4/8 read_early_config(): optionally return the worktree's top-level directoryJohannes Schindelin, Jun 8, 2017
  7. Jeff KingJun 10, 2017
  8. 1/8 discover_git_directory(): avoid setting invalid git_dirJohannes Schindelin, Jun 8, 2017
  9. Jeff KingJun 10, 2017
  10. 3/8 help: use early config when autocorrecting aliasesJohannes Schindelin, Jun 8, 2017
  11. Jeff KingJun 10, 2017
  12. 5/8 t1308: relax the test verifying that empty alias values are disallowedJohannes Schindelin, Jun 8, 2017
  13. Junio C HamanoJun 10, 2017
  14. Johannes SchindelinJun 13, 2017
  15. Junio C HamanoJun 13, 2017
  16. 6/8 t7006: demonstrate a problem with aliases in subdirectoriesJohannes Schindelin, Jun 8, 2017
  17. 8/8 Use the early config machinery to expand aliasesJohannes Schindelin, Jun 8, 2017
  18. Jeff KingJun 10, 2017
  19. Jeff KingJun 10, 2017
  20. Junio C HamanoJun 12, 2017
  21. Johannes SchindelinJun 13, 2017
  22. Jeff KingJun 13, 2017
  23. 7/8 alias_lookup(): optionally return top-level directoryJohannes Schindelin, Jun 8, 2017
  24. Jeff KingJun 10, 2017
  25. Johannes SchindelinJun 13, 2017
  26. Jeff KingJun 13, 2017
  27. Johannes SchindelinJun 13, 2017
  28. Jeff KingJun 13, 2017
  29. Junio C HamanoJun 13, 2017
  30. Jeff KingJun 14, 2017
  31. Johannes SchindelinJun 14, 2017
  32. Brandon WilliamsJun 8, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.