git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Galvin <agalvin@comqi.com>
To: Junio C Hamano <gitster@pobox.com>,
	Alex Galvin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] git-svn: use svn:global-ignores when creating .gitignores
Date: Thu, 18 Jul 2024 15:59:14 -0400	[thread overview]
Message-ID: <ba217f0c-68db-4e66-9397-c8819589371e@comqi.com> (raw)
In-Reply-To: <xmqqed7r3fyv.fsf@gitster.g>


On 2024-07-17 4:45 p.m., Junio C Hamano wrote:
> Paying attention to the new property and get it reflected to
> .gitignore on Git side may be a reasonable solution, especially if
> we ignore older version of Subversion.  But I have a naïve question.
> If a new version of git-svn starts to rely on the new property that
> is only available in SVN 1.8, would it create problems with folks
> whose SVN installation does not understand it?  Would it cause
> problems to them?

I don't believe so. Git doesn't do anything to set these properties,
it just reads and translates them into the format used by .gitignore.
So users on old versions of SVN should not be affected, their
servers will not have this property set anywhere.

> Anyway, in this project, explanation of the problem the patches
> address, with the outline of the solution, should be in the proposed
> commit log message of the patches themselves, not just written in
> the cover letter.  Can you redo the proposed log messages of these
> two patches, where you have none in this iteration?
>
> Thanks.
Sure thing. An amended patchset is incoming.

Thanks,
Alex

  reply	other threads:[~2024-07-18 19:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 19:57 [PATCH 0/2] git-svn: use svn:global-ignores when creating .gitignores Alex Galvin via GitGitGadget
2024-07-17 19:57 ` [PATCH 1/2] git-svn: add public property `svn:global-ignores` Alex Galvin via GitGitGadget
2024-07-17 19:57 ` [PATCH 2/2] git-svn: use `svn:global-ignores` to create .gitignore Alex Galvin via GitGitGadget
2024-07-17 20:45 ` [PATCH 0/2] git-svn: use svn:global-ignores when creating .gitignores Junio C Hamano
2024-07-18 19:59   ` Alex Galvin [this message]
2024-07-18 20:47 ` [PATCH v2 " Alex Galvin via GitGitGadget
2024-07-18 20:47   ` [PATCH v2 1/2] git-svn: add public property `svn:global-ignores` Alex Galvin via GitGitGadget
2024-07-18 20:47   ` [PATCH v2 2/2] git-svn: use `svn:global-ignores` to create .gitignore Alex Galvin via GitGitGadget
2024-08-12 16:58   ` [PATCH v3 0/3] git-svn: use svn:global-ignores when creating .gitignores Alex Galvin via GitGitGadget
2024-08-12 16:58     ` [PATCH v3 1/3] git-svn: add public property `svn:global-ignores` Alex Galvin via GitGitGadget
2024-08-12 16:58     ` [PATCH v3 2/3] git-svn: use `svn:global-ignores` to create .gitignore Alex Galvin via GitGitGadget
2024-08-12 16:58     ` [PATCH v3 3/3] git-svn: mention `svn:globalignores` in help Alex Galvin via GitGitGadget
2024-08-12 20:39     ` [PATCH v3 0/3] git-svn: use svn:global-ignores when creating .gitignores Junio C Hamano

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=ba217f0c-68db-4e66-9397-c8819589371e@comqi.com \
    --to=agalvin@comqi.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.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).