Closed
Bug 322600
Opened 19 years ago
Closed 19 years ago
Bump up version to 1.1a on MOZILLA_1_8_BRANCH
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey1.1alpha
People
(Reporter: iannbugzilla, Assigned: iannbugzilla)
Details
(Keywords: fixed-seamonkey1.1a, fixed1.8.1)
Attachments
(1 file, 1 obsolete file)
1.17 KB,
patch
|
Biesinger
:
review+
Biesinger
:
approval-seamonkey1.1a+
|
Details | Diff | Splinter Review |
Now MOZILLA_1_8_0_BRANCH has been created the version off SeaMonkey on the 1.8 branch should be changed from 1.0b to 1.1a
Assignee: general → iann_bugzilla
Status: NEW → ASSIGNED
Attachment #207758 -
Flags: review?
Attachment #207758 -
Flags: approval-seamonkey1.1?
Attachment #207758 -
Flags: review? → review?(cst)
Comment 2•19 years ago
|
||
Comment on attachment 207758 [details] [diff] [review] Does the deed v0.1 I know you didn't ask me for it, but as I did the last version changes, I guess I'm fitting :) Please care to not insert a newline into version.txt - the rest looks fine to me.
Attachment #207758 -
Flags: review?(cst)
Attachment #207758 -
Flags: review+
Attachment #207758 -
Flags: approval-seamonkey1.1?
Attachment #207758 -
Flags: approval-seamonkey1.1+
If I knew how to do that I would but even doing echo 1.1a > version.txt seems to add somesort of endofline marker.
Comment 4•19 years ago
|
||
echo -n But that said... this file really ought to work with an EOL sign.
Comment 5•19 years ago
|
||
Note that firefox does have a newline there: $ xxd ~/mozilla/browser/config/version.txt 0000000: 312e 3661 310a 1.6a1.
Comment 6•19 years ago
|
||
biesi: You just need to correctly change to configure.in line to exclude the newline then, IMO. We surely don't want MOZ_APP_VERSION to contain the newline.
Comment 7•19 years ago
|
||
I don't think so (even ignoring the fact that this works for ffox): [15:25:53 chb@christian tmp]$ echo 1.1a > bar [15:25:56 chb@christian tmp]$ export x=`cat bar` [15:26:14 chb@christian tmp]$ env|grep ^x= x=1.1a [15:26:19 chb@christian tmp]$ No additional newline.
So with or without new line then? Other question is do we move to the same as FF and use 1,1a,0,0 instead of 1,1,0,0?
Comment 9•19 years ago
|
||
(In reply to comment #8) > So with or without new line then? > Other question is do we move to the same as FF and use 1,1a,0,0 instead of > 1,1,0,0? I would add the newline and go for 1,1a,0,0
Assignee | ||
Comment 10•19 years ago
|
||
As biesi suggests
Attachment #207758 -
Attachment is obsolete: true
Comment 11•19 years ago
|
||
Comment on attachment 207851 [details] [diff] [review] Doing a slightly different deed v0.1a (Checked into branch 1.8) r+a=me for MOZILLA_1_8_BRANCH
Attachment #207851 -
Flags: review+
Attachment #207851 -
Flags: approval-seamonkey1.1+
Assignee | ||
Comment 12•19 years ago
|
||
Comment on attachment 207851 [details] [diff] [review] Doing a slightly different deed v0.1a (Checked into branch 1.8) Checking in (branch 1.8) module.ver; new revision: 1.4.2.2; previous revision: 1.4.2.1 version.txt; new revision: 1.1.4.2; previous revision: 1.1.4.1 done
Attachment #207851 -
Attachment description: Doing a slightly different deed v0.1a → Doing a slightly different deed v0.1a (Checked into branch 1.8)
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
Whiteboard: fixed-seamonkey1.1
Keywords: fixed-seamonkey1.1
Whiteboard: fixed-seamonkey1.1
You need to log in
before you can comment on or make changes to this bug.
Description
•