linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: linux-man@vger.kernel.org, Suren Baghdasaryan <surenb@google.com>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Matthew Wilcox <willy@infradead.org>,
	Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
	linux-mm@kvack.org
Subject: git repositories and branches (was: [PATCH man-pages v4] madvise.2: ...)
Date: Thu, 5 Dec 2024 13:43:58 +0100	[thread overview]
Message-ID: <20241205124358.l4vzdinfzqngl7pn@devuan> (raw)
In-Reply-To: <e7e1d068-af82-4b48-9fde-a341158e4db0@lucifer.local>

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

Hi Lorenzo,

On Thu, Dec 05, 2024 at 12:26:56PM +0000, Lorenzo Stoakes wrote:
> On Thu, Dec 05, 2024 at 01:20:37PM +0100, Alejandro Colomar wrote:
> > Thanks for the patch!  I've applied it, with some minor tweaks.  See
> > comments below.
> > <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=bb405ee3f6039226267fb1c6d2cb1fbb18d835bf>
> 
> Thanks all seems reasonable.
> 
> Just a quick question for future changes - I see you reference
> git://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git - but
> I've been working against
> git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git - is the latter
> occasionally synced from the former?

The 'main' branch in that server is usually at the same point that
'master' at <kernel.org>.  They're the same thing, just on different
servers.

Then, there's a 'contrib' branch in my server, which I use to buffer
patches I apply from others.  That allows me to amend typos and other
mistakes (or even drop patches) before pushing to master.

Here's my workflow:

1)  I push always first to 'contrib', which triggers CI on my server,
    and lets me know if all's good (it runs many linters set up in the
    build system).

2)  Then I let know the contributor I've pushed there.  Then I leave it
    there for a day or so.

3)  If I don't find anything wrong in a day or so, I push to 'main' in
    my server, which regenerates the PDF book in my website:
    <https://www.alejandro-colomar.es/share/dist/man-pages/git/HEAD/man-pages-HEAD.pdf>.

4)  After the PDF is generated correctly, I push to <kernel.org>'s
    'master'.

You can think of this contrib branch as a 'next' from the kernel, but I
pull from it much more often.

> Or should I be working against your
> personal repo for future changes?

Most of the time, it's enough to use the 'master' branch from
<kernel.org>.

In some cases, for example if you have several patches for a single
page, if I have applied some of them, and you need to rebase, it would
make sense to base on that 'contrib' branch.  Or if I have applied some
changes recently to it and might conflict with yours, I'll ask you to
rebase.

Cheers,
Alex

> 
> Thanks, Lorenzo

-- 
<https://www.alejandro-colomar.es/>

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

  reply	other threads:[~2024-12-05 12:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 10:41 [PATCH man-pages v4] madvise.2: add MADV_GUARD_INSTALL, MADV_GUARD_REMOVE description Lorenzo Stoakes
2024-12-05 12:20 ` Alejandro Colomar
2024-12-05 12:26   ` Lorenzo Stoakes
2024-12-05 12:43     ` Alejandro Colomar [this message]
2024-12-05 13:06       ` git repositories and branches (was: [PATCH man-pages v4] madvise.2: ...) Lorenzo Stoakes
2024-12-05 17:50 ` [PATCH man-pages v4] madvise.2: add MADV_GUARD_INSTALL, MADV_GUARD_REMOVE description Vlastimil Babka
2024-12-05 18:09   ` Lorenzo Stoakes
2024-12-05 20:43     ` Vlastimil Babka
2024-12-05 22:53       ` Alejandro Colomar
2024-12-06 11:03       ` Lorenzo Stoakes
2024-12-06 11:22         ` Lorenzo Stoakes

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=20241205124358.l4vzdinfzqngl7pn@devuan \
    --to=alx@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=jannh@google.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox