All of lore.kernel.org
 help / color / mirror / Atom feed
From: Germano Percossi <germano.percossi@citrix.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2-tools repository and documentation
Date: Mon, 15 Dec 2014 18:47:02 +0000	[thread overview]
Message-ID: <548F2CA6.4060707@citrix.com> (raw)
In-Reply-To: <548D3B1E.5030309@suse.de>

Hi Goldwyn,

Thanks for your answer. I will have a look at your code.
I just want to be sure that the source code I am looking at
is the latest one to avoid fixing things that maybe have been already
fixed elsewhere.

Same is true for documentation and package repositories.
If I could have links to the latest, no matter how old and not
maintained, documentation and repository, it would be helpful,
as well.

Do you know of any other distro, besides Suse, maintaining a stack
of patches?

Cheers,
Germano

On 14/12/14 07:24, Goldwyn Rodrigues wrote:
>
> Yes, if you don't count the last 2 patches, it is more close to 3 years
> now ;)
>
> Since the patches were not being updated. I started maintaining an
> alternate repository where I am putting all the bugs reported at SUSE:
>
> https://github.com/goldwynr/ocfs2-tools
>
> Branch suse-fixes has the fixes found by SUSE over the "upstream" branch.
>
> Branch nocontrold has the patches for the feature of doing away with
> ocfs2_controld to work with the latest corosync/pacemaker stack. Patches
> for the kernel are already in the kernel but the ones in the tools need
> some review.
>
> I had a mail conversation with Srini and he has promised to update the
> upstream branch soon.
>
> Regards,
>

  reply	other threads:[~2014-12-15 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 19:32 [Ocfs2-devel] ocfs2-tools repository and documentation Germano Percossi
2014-12-14  7:24 ` Goldwyn Rodrigues
2014-12-15 18:47   ` Germano Percossi [this message]
2014-12-16  5:35     ` Srinivas Eeda
2014-12-16 17:43       ` Germano Percossi
2014-12-16 15:01     ` Goldwyn Rodrigues
2014-12-16 15:29     ` Goldwyn Rodrigues

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=548F2CA6.4060707@citrix.com \
    --to=germano.percossi@citrix.com \
    --cc=ocfs2-devel@oss.oracle.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 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.