From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Help with btrfs project
Date: Wed, 20 Aug 2014 07:49:45 -0400 [thread overview]
Message-ID: <33591.1408535385@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 19 Aug 2014 22:33:28 -0400." <CAPDOMVjj5_hjvWh2CokdOCs4t3tY-Q7gEcAnPufbgUiKswkinQ@mail.gmail.com>
On Tue, 19 Aug 2014 22:33:28 -0400, Nick Krause said:
> Other then the TODO list, which we can discuss here, is there any
> other parts of this patch that need to
> be rewritten, it's merged as of now
If this total turd of a patch was merged by an upstream maintainer, said
maintainer needs to be taken out back and shot.
And quite frankly, we don't care what you've merged into a local tree.
> is how you want this cleaned up.
Take it out back and shoot it.
> From: David Sterba <dsterba@suse.cz>
> Date: Thu, 19 Apr 2012 15:09:09 +0200
> Subject: [PATCH 1/1] btrfs: ioctl to clear unused space
Nick, you were *told* to quit trying to evade banishments by changing
names. If this is actually from a Suse developer, they are perfectly
able to do their own work and upstream it. If this is a patch from
2012 and *still* not upstreamed, there's probably good reasons for it.
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -3580,7 +3580,7 @@ again:
> if (btrfs_test_opt(root, DISCARD))
> ret = btrfs_error_discard_extent(root, start,
> end + 1 - start,
> - NULL);
> + NULL, 1);
I don't know *what* you did to your git tree, but this is *not* how
kernel code is formatted. People who submit code that's *THIS* poorly
formatted even after they've been warned before are *not* welcome
in the kernel community.
I'm sorry Nick, but you've worn out pretty much all of whatever little
welcome you had left.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140820/abf0a50b/attachment.bin
prev parent reply other threads:[~2014-08-20 11:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 2:33 Help with btrfs project Nick Krause
2014-08-20 5:14 ` Sudip Mukherjee
2014-08-20 11:50 ` Valdis.Kletnieks at vt.edu
2014-08-20 12:11 ` Sudip Mukherjee
2014-08-20 15:46 ` Jason Conklin
2014-08-20 16:33 ` Mandeep Sandhu
2014-08-20 17:15 ` Lidza Louina
2014-08-20 17:20 ` Nick Krause
2014-08-20 17:24 ` Nick Krause
2014-08-20 17:25 ` Philipp Muhoray
2014-08-20 17:30 ` Nick Krause
2014-08-20 17:33 ` Nick Krause
2014-08-20 17:58 ` Sudip Mukherjee
2014-08-20 21:25 ` Nick Krause
2014-08-20 23:58 ` Andrej Manduch
2014-08-20 23:59 ` Andrej Manduch
2014-08-21 0:21 ` Bernd Petrovitsch
2014-08-21 2:47 ` Nick Krause
2014-08-21 4:18 ` Nick Krause
2014-08-20 15:22 ` Philipp Muhoray
2014-08-20 11:49 ` Valdis.Kletnieks at vt.edu [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=33591.1408535385@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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.