Re: patch submits

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2013-11-13 at 12:12 -0500, Gene Czarcinski wrote:
> I was wondering what the protocol is for submitting patches.
> 
> Recently, (November 8th), I submitted a two part patch (anaconda and 
> pykickstart) which implements new functionality adding the "reclaim" 
> option to the kickstart btrfs command.
> 
> The reclaim option (the name was chosen because of the similar function 
> available in non-kickstart custom disk allocation) allows an existing 
> btrfs subvolume to be specified for mountpoints such as root where the 
> subvolume's filesystem/device must be destroyed before the can be newly 
> created using the same name.  This will also recover (reclaim) the disk 
> space used by the previous subvolume.
> 
> Now, at this late date, there is not way that I expect this to be 
> incorporated into Fedora 20.  However, having this languish on the 
> patches mailing list can also have it easily forgotten.
> 
> So, for non-official anaconda/pykickstart/blivet/etc. developers who 
> submit patches, what should we expect to happen.  If something does not 
> happen withing <?> should we "ping" this or the patches mailing list?
Yes, feel free to "ping" us on the patches list. It sometimes happens
that patches stay unreviewed for a long time and may get forgotten
completely then.

-- 
Vratislav Podzimek

Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list




[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux