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

Re: [PATCH] format-patch: remove existing output-directory

From
Fredrik Gustafsson <iveqy@iveqy.com>
Date
Jun 14, 2013, 13:16 UTC
Message-ID
<20130614131629.GA1086@paksenarrion.iveqy.com>
In-Reply-To
<1371213813-7925-1-git-send-email-artagnon@gmail.com>

Hi, just some questions about your patch.

On Fri, Jun 14, 2013 at 06:13:33PM +0530, Ramkumar Ramachandra wrote:
Show 8 quoted lines
> The following command
> 
>   $ git format-patch -o outgoing master
> 
> does not ensure that the output-directory outgoing doesn't already
> exist.  As a result, it's possible for patches from two different series
> to get mixed up if the user is not careful.  Fix the problem by
> unconditionally removing the output-directory before writing to it.

I'm not entirely happy about removing untracked stuff without asking the user. What if the output directory isn't empty? What if a user just want them in ~?

However I think this patch can improve the workflow for experienced developers. Can we tweak this in some way to get the best out of both worlds?

Show 6 quoted lines
> +		struct strbuf buf = STRBUF_INIT;
> +
>  		if (use_stdout)
>  			die(_("standard output, or directory, which one?"));
> +		strbuf_addstr(&buf, output_directory);
> +		remove_dir_recursively(&buf, 0);
Should we have a strbuf_release here?
-- 
Med vänliga hälsningar
Fredrik Gustafsson

tel: 0733-608274
e-post: iveqy@iveqy.com
Previous: Junio C HamanoNext: Ramkumar Ramachandra
Message 7 of 12 in “format-patch: remove existing output-directory”
  1. format-patch: remove existing output-directoryRamkumar Ramachandra, Jun 14, 2013
  2. John KeepingJun 14, 2013
  3. Ramkumar RamachandraJun 14, 2013
  4. John KeepingJun 14, 2013
  5. Junio C HamanoJun 14, 2013
  6. Junio C HamanoJun 14, 2013
  7. Fredrik GustafssonJun 14, 2013
  8. Ramkumar RamachandraJun 14, 2013
  9. Fredrik GustafssonJun 14, 2013
  10. Ramkumar RamachandraJun 14, 2013
  11. SZEDER GáborJun 14, 2013
  12. Ramkumar RamachandraJun 14, 2013

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.