1 |
On Mon, May 14, 2012 at 05:26:44PM +0200, Michael Scherer wrote: |
2 |
> in my opinion it isn't. with top posting I see the newest message |
3 |
> immidiately, while otherwise I need page through sometimes |
4 |
> huge amounts of mostly obsolete comments. |
5 |
> where it's possible, I put my messages on top, and I've found |
6 |
> more than once forum-rules that require or at least recommend |
7 |
> top posting. |
8 |
> but I garantee that I will get flames, why I do this and urge me |
9 |
> to change my habits. |
10 |
> obviously this is an ingrained habit on gentoo-users, but from |
11 |
> now on I'm going follow my habits and damn the flames. |
12 |
> |
13 |
> regards |
14 |
> |
15 |
> michael |
16 |
> |
17 |
> -- |
18 |
> Michael Scherer |
19 |
> Univ.klinik f. Psychiatrie |
20 |
> email: michael.scherer@×××××××××××××.at |
21 |
> phone: +43 6991 941 22 54 |
22 |
> |
23 |
> ----- Original Message ----- |
24 |
> From: <ny6p01@×××××.com> |
25 |
> To: <gentoo-user@l.g.o> |
26 |
> Sent: Monday, 14 May, 2012 04:13 |
27 |
> Subject: Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails |
28 |
> |
29 |
> |
30 |
> > A: Because it messes up the order in which people normally read text. |
31 |
> > |
32 |
> > On Mon, May 14, 2012 at 03:44:31AM +0200, Michael Scherer wrote: |
33 |
> > |
34 |
> >> regrettably no. at this point make (correctly) assumes that mounts.o |
35 |
> >> should have been built, but it didn't. |
36 |
> >> sorry for my delayed replay, I've tried I lot of possibilities, needless |
37 |
> >> to say without success. |
38 |
> >> |
39 |
> >> thanks |
40 |
> >> |
41 |
> >> michael |
42 |
> >> |
43 |
> >> -- |
44 |
> >> Michael Scherer |
45 |
> >> Univ.klinik f. Psychiatrie |
46 |
> >> email: michael.scherer@×××××××××××××.at |
47 |
> >> phone: +43 6991 941 22 54 |
48 |
> >> |
49 |
> >> ----- Original Message ----- |
50 |
> >> From: "walt" <w41ter@×××××.com> |
51 |
> >> To: <gentoo-user@l.g.o> |
52 |
> >> Sent: Saturday, 12 May, 2012 20:17 |
53 |
> >> Subject: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails |
54 |
> >> |
55 |
> >> |
56 |
> >> > On 05/10/2012 07:20 AM, Michael Scherer wrote: |
57 |
> >> >> LD init/mounts.o |
58 |
> >> >> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o |
59 |
> >> >> init/do_mounts_initrd.o init/mounts.o: No such file or directory |
60 |
> >> > |
61 |
> >> > Maybe that step is correct but it sure looks strange to me. Looks |
62 |
> >> > like 'ls' is being substituted for 'ld', maybe? Is that a cut-and- |
63 |
> >> > paste error? |
64 |
> > |
65 |
> > Q: Why is top-posting such a bad thing? |
66 |
|
67 |
http://linux.sgms-centre.com/misc/netiquette.php |
68 |
|
69 |
******* |
70 |
|
71 |
Below are a set of rules by which you should try and abide whenever posting |
72 |
to a public area such as USENET or a mailing list. They are designed with |
73 |
one thing in mind: being polite to your fellow netizens. Failure to do so |
74 |
can make you look at best inconsiderate, if not plain stupid, or even lead |
75 |
more "seasoned" netizens to believe that you're trolling (deliberately |
76 |
stirring up a fuss in order to draw attention to yourself and/or start up a |
77 |
fight - or flamefest). In the long run you'll just get yourself PLONKED |
78 |
(added to people's killfiles so they no longer have to read what you have to |
79 |
say), which is fairly counter-productive if your intentions are worthy. |
80 |
|
81 |
You can avoid yourself this embarrassment (and everybody else's displeasure) |
82 |
by following the basic rules described here: |
83 |
|
84 |
... |
85 |
|
86 |
9. DO NOT TOP-POST and DO trim your replies!!! Top-posting is the annoying |
87 |
practice of replying to a message by typing your response above that to |
88 |
which you are responding. This is a _Bad Thing_ because your readers will |
89 |
have to scroll down and extract the essential of the existing thread in |
90 |
order to grasp the context of your reply, and then scroll back up again to |
91 |
read your reply. Posting a "me too" comment at the bottom of a 100+ line |
92 |
message is no better because people, have to scroll all the way down through |
93 |
100+ lines they've already read in order to see your one-liner. One word |
94 |
comes to mind for that: frustrating. The generally accepted "right way" of |
95 |
doing things is called "inline posting", whereby you insert your comments |
96 |
straight after that on which you are commenting, having stripped |
97 |
unnecessary text from the original quoted text. The end result is something |
98 |
which makes much more sense because it reads like a conversation. |
99 |
|
100 |
******** |
101 |
|
102 |
Remember, in a list, you are not only writing for the person who you are |
103 |
responding to. You are posting for whoever may be interested in the topic. |
104 |
While I appreciate that you may not benefit from top posting since you know |
105 |
the context, this is not true for someone who has linked to your message or |
106 |
who is reading it days, weeks or years later. :) |
107 |
|
108 |
Terry |