All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Simon Richter <sjr@debian.org>
Cc: git@vger.kernel.org,  debian-devel@lists.debian.org
Subject: Re: Representing Debian Metadata in Git
Date: Fri, 23 Aug 2024 10:20:19 +0800	[thread overview]
Message-ID: <874j7cou8s.fsf@melete.silentflame.com> (raw)
In-Reply-To: <eb963843-9e2c-49f2-911f-fa36f33f9bfd@debian.org> (Simon Richter's message of "Tue, 20 Aug 2024 16:10:34 +0900")

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Hello,

I think that more than you realise of this already exists :)

On Tue 20 Aug 2024 at 04:10pm +09, Simon Richter wrote:

> From a requirements perspective, I'd like to be able to
>
>  - express patches as commits:
>    - allow cherry-picking upstream commits as Debian patches
>    - allow cherry-picking Debian patches for upstream submission

git-debrebase and git-dpm already achieve this.

>  - express filter steps for generating the upstream archive(s) from a tree‑ish
>   and some metadata

Excluded-Files in d/copyright is for this.
I guess that you disprefer that because it's part of the tree, though.

>  - store upstream signatures inside Git

Well, there's signatures on their tags.

>  - keep a history of patches, including patches applied to previously released
>   packages

This is already there with git-debrebase and git-dpm, though it is a bit
fiddly to dig it out.

-- 
Sean Whitton

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]

      parent reply	other threads:[~2024-08-23  2:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  7:10 Representing Debian Metadata in Git Simon Richter
2024-08-21 21:37 ` Chris Hofstaedtler
2024-08-21 23:11   ` rsbecker
2024-08-21 23:51     ` Chris Hofstaedtler
2024-08-22 19:27 ` Blair Noctis
2024-08-23  2:20 ` Sean Whitton [this message]

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=874j7cou8s.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=debian-devel@lists.debian.org \
    --cc=git@vger.kernel.org \
    --cc=sjr@debian.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.