On 12/11/2024 8:15 pm, Jürgen Spitzmüller wrote:
Am Dienstag, dem 12.11.2024 um 10:53 +1300 schrieb Andrew Parsloe:
I am still able to log in to trac, but I find my name displays in
bold
type, which is embarrassing, and my email address dates back about a
decade and is no longer valid. When I
Am Dienstag, dem 12.11.2024 um 10:53 +1300 schrieb Andrew Parsloe:
> I am still able to log in to trac, but I find my name displays in
> bold
> type, which is embarrassing, and my email address dates back about a
> decade and is no longer valid. When I try to change thing
I am still able to log in to trac, but I find my name displays in bold
type, which is embarrassing, and my email address dates back about a
decade and is no longer valid. When I try to change things (in trac's
Preferences) and press the submit changes button nothing permanent seems
to h
On Thu, Sep 26, 2024 at 12:17:48AM +, Georger Araujo wrote:
> Hi,
> I would like to report a bug but I forgot my Trac password (username:
> georger.araujo) and it seems the 'Forgot password?' link is not available in
> the Trac login screen. So I report it here. Sorry f
Hi,
I would like to report a bug but I forgot my Trac password (username:
georger.araujo) and it seems the 'Forgot password?' link is not available in
the Trac login screen. So I report it here. Sorry for the trouble.
Title: LilyPond preview does not work with LilyPond 2.24.1
L
Sent privately.
Jürgen
Am Donnerstag, dem 18.07.2024 um 12:51 +0900 schrieb Yokota K.:
> To the manager of Trac:
>
> Hi, I tried to post to Trac and found I seem to have lost my Trac
> password.
> Could you kindly reset it? If my user ID is needed, I will send it
> per
To the manager of Trac:
Hi, I tried to post to Trac and found I seem to have lost my Trac password.
Could you kindly reset it? If my user ID is needed, I will send it personally.
Koji
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Hi all,
we tried to open our trac for registration again and got thousands of new
accounts during last weeks. Tonight those accounts started creating bug
reports which were essentially ads.
I banned the registration (again) and made big cleanup. trac interface
is unfortunately such that large
> I sent new login privately. P
It worked, thanks!
I'm going to report the bugs there so you got them thrice :)
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Wed, Mar 13, 2024 at 09:19:45PM -0300, Carlos Pita wrote:
> I've been trying to report a couple of bugs to your Trac (which I
> haven't used for ages) but to no avail. I've a password although it
> doesn't seem to be the right one, so I tried to reset my passwo
Hi guys,
I've been trying to report a couple of bugs to your Trac (which I
haven't used for ages) but to no avail. I've a password although it
doesn't seem to be the right one, so I tried to reset my password many
times but the email never arrived to my inbox (nor spam folde
On 2/13/24 15:39, Pavel Sanda wrote:
On Tue, Feb 13, 2024 at 06:11:51PM +0100, Jean-Pierre Chrétien wrote:
I see, you mean in documentation not in trac. It's not that simple, we are
currently working on transition of trac itself so in medium term this
link might be working again. Or not
On Tue, Feb 13, 2024 at 06:11:51PM +0100, Jean-Pierre Chrétien wrote:
> >I see, you mean in documentation not in trac. It's not that simple, we are
> >currently working on transition of trac itself so in medium term this
> >link might be working again. Or not ;)
> >I
Le 12/02/2024 à 21:33, Pavel Sanda a écrit :
On Mon, Feb 12, 2024 at 05:01:32PM +0100, Jean-Pierre Chrétien wrote:
BTW, I will update the reference of the documentation in trac with
https://git.lyx.org/gitweb/?p=lyx.git;a=tree;f=lib/doc;hb=HEAD
Where exactly in the trac do you want to make
On Mon, Feb 12, 2024 at 05:01:32PM +0100, Jean-Pierre Chrétien wrote:
> >>>BTW, I will update the reference of the documentation in trac with
> >>>https://git.lyx.org/gitweb/?p=lyx.git;a=tree;f=lib/doc;hb=HEAD
> >>
> >>Where exactly in the trac do
Here I change the subject for what concerns th change from trac to git.lyx.org.
Sorry if it is not the correct procedure.
Would it be better located in lyx-docs ? I understood that cross-posting is not
a good practice.
Le 12/02/2024 à 16:45, Jean-Pierre Chrétien a écrit :
BTW, I will
Am Mo., 3. Juli 2023 um 23:31 Uhr schrieb Pavel Sanda:
> On Mon, Jun 26, 2023 at 07:18:24PM +0200, Yu Jin wrote:
> > > We do not know why this is happening, but we can reset the password for
> > > you.
> > >
> > Yeah sure. Additionally if it is just gmail, maybe just update my
> account's
> > emai
On Mon, Jun 26, 2023 at 07:18:24PM +0200, Yu Jin wrote:
> > We do not know why this is happening, but we can reset the password for
> > you.
> >
> Yeah sure. Additionally if it is just gmail, maybe just update my account's
> email address to yu_...@lyx.org? If that forwarding is still up.
I tried
fications became essentialy
>> unusable fro anyone having gmail address.
>>
>> I also figured out that whatever we sent to Eugene for windows OS in trac
>> probably did not reach target, because I do not see his account (Yu_Jin)
>> on
>> trac. Either never was there
out that whatever we sent to Eugene for windows OS
in trac
probably did not reach target, because I do not see his account
(Yu_Jin) on
trac. Either never was there or we lost it...
Eugene, are you around still? Should we create an account for you?
There are
some bugs, wh
sent to Eugene for windows OS in trac
> probably did not reach target, because I do not see his account (Yu_Jin) on
> trac. Either never was there or we lost it...
>
> Eugene, are you around still? Should we create an account for you? There
> are
> some bugs, which need attention from so
I changed my email address on Trac to a non-gmail address, and now I receive
email notifications again, whereas I didn't when I was using a gmail account.
On Fri, Jun 16, 2023, at 7:27 AM, Pavel Sanda wrote:
> On Fri, Jun 16, 2023 at 10:53:39AM +0200, Pavel Sanda wrote:
> > I wond
On Fri, Jun 16, 2023 at 10:53:39AM +0200, Pavel Sanda wrote:
> I wonder whether our bug tracker notifications became essentialy unusable fro
> anyone having gmail address.
I also figured out that whatever we sent to Eugene for windows OS in trac
probably did not reach target, because I
On 16.06.2023 12:17, Pavel Sanda wrote:
On Fri, Jun 16, 2023 at 06:01:48AM -0400, Scott Kostyshak wrote:
On Fri, Jun 16, 2023 at 11:52:56AM +0200, Pavel Sanda wrote:
On Fri, Jun 16, 2023 at 05:42:08AM -0400, Scott Kostyshak wrote:
I'm still using GMail. I don't remember how I set things up th
Le 16/06/2023 à 12:17, Pavel Sanda a écrit :
On Fri, Jun 16, 2023 at 06:01:48AM -0400, Scott Kostyshak wrote:
On Fri, Jun 16, 2023 at 11:52:56AM +0200, Pavel Sanda wrote:
On Fri, Jun 16, 2023 at 05:42:08AM -0400, Scott Kostyshak wrote:
I'm still using GMail. I don't remember how I set things
On Fri, Jun 16, 2023 at 06:01:48AM -0400, Scott Kostyshak wrote:
> On Fri, Jun 16, 2023 at 11:52:56AM +0200, Pavel Sanda wrote:
> >
> > On Fri, Jun 16, 2023 at 05:42:08AM -0400, Scott Kostyshak wrote:
> > > I'm still using GMail. I don't remember how I set things up though. I do
> > > receive not
On Fri, Jun 16, 2023 at 11:52:56AM +0200, Pavel Sanda wrote:
>
> On Fri, Jun 16, 2023 at 05:42:08AM -0400, Scott Kostyshak wrote:
> > I'm still using GMail. I don't remember how I set things up though. I do
> > receive notifications.
>
> Nope, you are using @lyx.org forward. P
Ah, good to know
On Fri, Jun 16, 2023 at 05:42:08AM -0400, Scott Kostyshak wrote:
> I'm still using GMail. I don't remember how I set things up though. I do
> receive notifications.
Nope, you are using @lyx.org forward. P
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx
On Fri, Jun 16, 2023 at 10:53:39AM +0200, Pavel Sanda wrote:
>
> Hi,
>
> I wonder whether our bug tracker notifications became essentialy unusable fro
> anyone having gmail address.
>
> Is there anyone registered in trac with gmail address who still recieves
> notifica
Hi,
I wonder whether our bug tracker notifications became essentialy unusable fro
anyone having gmail address.
Is there anyone registered in trac with gmail address who still recieves
notifications for bug activities (like replies)
or are we essentially cut from feedback for ayone using gmail
On Thu, Jun 15, 2023 at 01:47:13PM -0400, Alexander Dunlap wrote:
> I have had problems with the LyX trac for some time in that I do not receive
> email notifications. Now I have a new problem, which is that I am locked out
> of my account (I do not know why as I did not change the
Hi all,
I have had problems with the LyX trac for some time in that I do not receive
email notifications. Now I have a new problem, which is that I am locked out of
my account (I do not know why as I did not change the password), and since the
emails to reset the password are not received for
On 5/15/23 05:40, Yuriy Skalko wrote:
Dear devs, >> >> >> I can't seem to access the bug reporter. Using my usual login
info >> gives me an "invalid password or username" error. Attempting to
>> restore the passoword results in the mail not being sent. >> >> >> I
was just able to log in. I'll
Dear devs,
I can't seem to access the bug reporter. Using my usual login info
gives me an "invalid password or username" error. Attempting to restore
the passoword results in the mail not being sent.
I was just able to log in. I'll privately send you a temporary password.
Riki
On 5/13/23 14:18, lorenzobertin...@gmail.com wrote:
Dear devs,
I can't seem to access the bug reporter. Using my usual login info
gives me an "invalid password or username" error. Attempting to restore
the passoword results in the mail not being sent.
I was just able to log in. I'll privately
Dear devs,
I can't seem to access the bug reporter. Using my usual login info
gives me an "invalid password or username" error. Attempting to restore
the passoword results in the mail not being sent.
Is the problem only on my end?
Cheers
--
Lorenzo
--
lyx-devel mailing list
lyx-devel@lists.lyx
Il 01/09/22 16:01, Jean-Marc Lasgouttes ha scritto:
Le 29/08/2022 à 09:14, Jürgen Spitzmüller a écrit :
Has anyone found a solution?
We'll have to wait until somebody with access to the database (Riki,
JMarc) is back.
I reverted to the passwords from August 12, and everything seems OK now.
Le 29/08/2022 à 09:14, Jürgen Spitzmüller a écrit :
Has anyone found a solution?
We'll have to wait until somebody with access to the database (Riki,
JMarc) is back.
I reverted to the passwords from August 12, and everything seems OK now.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.
Am Sonntag, dem 28.08.2022 um 22:44 +0200 schrieb Lorenzo Bertini:
> Bump!
>
> I'm getting the same message :(.
I suppose everybody does. Possibly we lost the user names once more.
> Has anyone found a solution?
We'll have to wait until somebody with access to the database (Riki,
JMarc) is bac
Bump!
I'm getting the same message :(. Has anyone found a solution?
Lorenzo
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 2022-08-16 13:38, Jean-Marc Lasgouttes wrote:
Hi Daniel,
I see your messages, but I do not have a way to connect to the server here.
JMarc
Le 16 août 2022 12:59:53 GMT+02:00, Daniel a écrit :
By the way, resetting the password does not help either.
Hi JMarc,
No problem! (I just wante
Hi Daniel,
I see your messages, but I do not have a way to connect to the server here.
JMarc
Le 16 août 2022 12:59:53 GMT+02:00, Daniel a écrit :
>By the way, resetting the password does not help either.
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo
On 13/08/2022 08:39, Kornel Benko wrote:
Am Sat, 13 Aug 2022 05:58:32 +0200
schrieb Daniel :
Anyone getting "Invalid username or password" when trying to login on
tract as well?
Daniel
Same here.
Kornel
By the way, resetting the password does not help either.
Daniel
--
lyx-d
Am Sat, 13 Aug 2022 05:58:32 +0200
schrieb Daniel :
> Anyone getting "Invalid username or password" when trying to login on
> tract as well?
>
> Daniel
>
>
Same here.
Kornel
pgpnkwTMX4Pnm.pgp
Description: Digitale Signatur von OpenPGP
--
lyx-devel mailing list
lyx-devel@lists.lyx.
Anyone getting "Invalid username or password" when trying to login on
tract as well?
Daniel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Tue, May 24, 2022 at 09:13:31PM +1200, Andrew Parsloe wrote:
> My computer is definitely showing the correct date and time for my location.
> (24 May 2022, about 9:05 pm New Zealand time when I tried.)
Most likely our certificate for lyx.org expired.
Pavel
--
lyx-devel mailing list
lyx-devel@l
I've just tried to view trac but Firefox prevented me with this message:
"Firefox detected an issue and did not continue to www.lyx.org. The
website is either misconfigured or your computer clock is set to the
wrong time. ... It’s likely the website’s certificate is expired, which
On 1/4/21 4:47 AM, Yu Jin wrote:
> Am Mo., 4. Jan. 2021 um 10:39 Uhr schrieb Yu Jin <mailto:yu_...@lyx.org>>:
>
> I am trying to search for bugs in Trac. I have chosen only "new"
> status in the filters, but the result also shows fixedinstable,
> reo
Am Mo., 4. Jan. 2021 um 10:39 Uhr schrieb Yu Jin :
> I am trying to search for bugs in Trac. I have chosen only "new" status in
> the filters, but the result also shows fixedinstable, reopened and even
> closed bugs in some cases. See attached.
> What am I doing wrong?
>
I am trying to search for bugs in Trac. I have chosen only "new" status in
the filters, but the result also shows fixedinstable, reopened and even
closed bugs in some cases. See attached.
What am I doing wrong?
--
Eugene
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lis
Lately, I often get errors from trac when I hit the submit/preview
button. It says:
Error: Bad Request
Missing or invalid form token. Do you have cookies enabled?
This happens only since a couple of weeks, I think. The workaround is to
navigate back and reload the page and hit submit
On 10/29/18 10:16 AM, Pavel Sanda wrote:
> On Mon, Oct 29, 2018 at 03:56:30PM +0200, Guy Rutenberg wrote:
>> https://www.lyx.org/robots.txt disallows search engines from the trac. Is
>> this intentional? It makes finding tickets in the trac much harder.
> IIRC It was intent
On Mon, Oct 29, 2018 at 03:56:30PM +0200, Guy Rutenberg wrote:
> https://www.lyx.org/robots.txt disallows search engines from the trac. Is
> this intentional? It makes finding tickets in the trac much harder.
IIRC It was intentional because some crawlers overloaded trac with requests
and
Hi,
https://www.lyx.org/robots.txt disallows search engines from the trac. Is
this intentional? It makes finding tickets in the trac much harder.
Thanks,
Guy
On 10/10/2018 08:29, Jean-Marc Lasgouttes wrote:
Le 9 octobre 2018 10:06:44 GMT+02:00, Daniel a écrit :
Actually, there seems to be no way in
trac to run this search query for "Summary contains 'labels' and
'moving'" since adding another Summary search field con
Le 9 octobre 2018 10:06:44 GMT+02:00, Daniel a écrit :
> Actually, there seems to be no way in
>trac to run this search query for "Summary contains 'labels' and
>'moving'" since adding another Summary search field connect them with
>"or" inst
On 10/10/2018 08:03, Jürgen Spitzmüller wrote:
Richard Kimberly Heck mailto:rikih...@lyx.org>>
schrieb am Mi., 10. Okt. 2018, 01:28:
Report it to the
trac folks?
Does this make sense as long as we run such an outdated version of trac?
Maybe not. I guess it is not a big p
Richard Kimberly Heck schrieb am Mi., 10. Okt. 2018,
01:28:
> Report it to the
> trac folks?
>
Does this make sense as long as we run such an outdated version of trac?
Jürgen
> Riki
>
>
On 10/09/2018 04:06 AM, Daniel wrote:
> I am probably missing something and this has been brought up before
> but the search function on trac seems severely limited. It seems
> impossible to search for the occurrence of words in a different order
> from how they appear in the text.
>
I am probably missing something and this has been brought up before but
the search function on trac seems severely limited. It seems impossible
to search for the occurrence of words in a different order from how they
appear in the text.
For example, search for "moving labels"
I've updated the "View Bugs" trac page, which is actually
https://www.lyx.org/trac/wiki/BugTrackerHome
to provide more useful info to developers. So now you will see a list of:
1. Bugs targeted to the next minor release (2.3.2, now) that have had
no attention yet.
2
Le 17/03/2018 à 21:44, Richard Kimberly Heck a écrit :
https redirects have now been established for lyx.org, wiki.lyx.org, and
git.lyx.org.
Please let me know if there are any problems.
Great news!
JMarc
Richard Kimberly Heck wrote:
> > That would help when I click on one of those old links sent by trac
> > notifications.
> >
> > Google.com or mozilla.org do redirect to https.
>
> https redirects have now been established for lyx.org, wiki.lyx.org, and
> git.lyx.
On Sat, Mar 17, 2018 at 08:44:52PM +, Richard Kimberly Heck wrote:
> Please let me know if there are any problems.
In brief testing, it works well!
Thanks,
Scott
signature.asc
Description: PGP signature
> permit them to do so, if they so wish. This would also provide some kind
>> of protection against https failures.
>
> That would help when I click on one of those old links sent by trac
> notifications.
>
> Google.com or mozilla.org do redirect to https.
https red
> permit them to do so, if they so wish. This would also provide some kind
>> of protection against https failures.
>
> That would help when I click on one of those old links sent by trac
> notifications.
>
> Google.com or mozilla.org do redirect to https.
Yes, my wor
n against https failures.
That would help when I click on one of those old links sent by trac
notifications.
Google.com or mozilla.org do redirect to https.
JMarc
On 02/22/2018 10:58 AM, Jean-Marc Lasgouttes wrote:
> Le 21/02/2018 à 18:14, Richard Heck a écrit :
>> I finally figured out how to make the links in the emails that trac
>> sends use https, so I have done that. Please let me know if there are
>> any issues.
>>
>
Le 21/02/2018 à 18:14, Richard Heck a écrit :
I finally figured out how to make the links in the emails that trac
sends use https, so I have done that. Please let me know if there are
any issues.
Great. And what about global redirection from http to https?
JMarc
On Wed, Feb 21, 2018 at 05:14:05PM +, Richard Heck wrote:
> I finally figured out how to make the links in the emails that trac
> sends use https, so I have done that. Please let me know if there are
> any issues.
Nice, thank you for doing that!
Scott
signature.asc
Descrip
I finally figured out how to make the links in the emails that trac
sends use https, so I have done that. Please let me know if there are
any issues.
Richard
On Mon, Jan 01, 2018 at 08:46:21AM +, Kornel Benko wrote:
> For instance:
>
> Ticket URL: <http://www.lyx.org/trac/ticket/10835#comment:17>
> The LyX Project <http://www.lyx.org/>
> LyX -- The Document Processor
I agree it would be nice to change those to ht
For instance:
Ticket URL: <http://www.lyx.org/trac/ticket/10835#comment:17>
The LyX Project <http://www.lyx.org/>
LyX -- The Document Processor
Kornel
signature.asc
Description: This is a digitally signed message part.
On Wed, Oct 18, 2017 at 08:56:50PM +, Richard Heck wrote:
> I realized a day or two ago that I wasn't myself sure how we are or
> should be using the "fixed in master" and "fixed in stable" statuses in
> Trac now that we have the 2.3.x branch. I.e., if somethi
I realized a day or two ago that I wasn't myself sure how we are or
should be using the "fixed in master" and "fixed in stable" statuses in
Trac now that we have the 2.3.x branch. I.e., if something is fixed in
the master branch and in 2.3.x, how is that to be noted? Ar
On Mon, Jun 26, 2017 at 10:32:29AM +0200, Jean-Marc Lasgouttes wrote:
> Le 25/06/2017 à 22:23, Scott Kostyshak a écrit :
> > To reproduce, go to:
> >
> > http://www.lyx.org/trac
> >
> > Then click on "login". The connection for enterin
Am Dienstag, 27. Juni 2017 um 10:19:45, schrieb Tim Hutt
> 1. Try to login with my usual username & password system.
> 2. Fails
> 3. Hmm I guess I forgot my password.
> 4. Enter username and email into the "Forgot my password" page.
>
> "The email and username do not match a known account."
>
>
1. Try to login with my usual username & password system.
2. Fails
3. Hmm I guess I forgot my password.
4. Enter username and email into the "Forgot my password" page.
"The email and username do not match a known account."
Ok what. That's stupid. You should only need the email address to
reset th
Le 26/06/2017 à 10:32, Jean-Marc Lasgouttes a écrit :
Le 25/06/2017 à 22:23, Scott Kostyshak a écrit :
To reproduce, go to:
http://www.lyx.org/trac
Then click on "login". The connection for entering your login and
password is not secure.
Note that it is secure if in the l
Le 25/06/2017 à 22:23, Scott Kostyshak a écrit :
To reproduce, go to:
http://www.lyx.org/trac
Then click on "login". The connection for entering your login and
password is not secure.
Note that it is secure if in the link I give above, https is used. I
think that the login l
To reproduce, go to:
http://www.lyx.org/trac
Then click on "login". The connection for entering your login and
password is not secure.
Note that it is secure if in the link I give above, https is used. I
think that the login link should always be secure.
Is this an easy fix
Just a random thought that I don't expect anyone to respond to and I'm
not interested in working on myself:
It would be nice to have a larger (set) interaction of the -dbg options
and our trac components. I keep thinking "clipboard" is a trac component
but it's not. Thi
It looks as if we have once again for some reason lost the entire
trac.htpasswd file. I noticed this because trac refused to accept my
password. I was able to reset it but then remembered what had happened
before. This may have been due to the disk's being full. In any event,
I've re
now how to debug trac.
JMarc
On Fri, Jun 03, 2016 at 02:07:35PM +0200, Jean-Marc Lasgouttes wrote:
> Le 02/06/2016 à 06:56, Scott Kostyshak a écrit :
> > Now the default milestone is blank, which is great. Can we also have the
> > version be blank by default? I think this would help, as discussed
> > before, so that we know if
Le 02/06/2016 à 06:56, Scott Kostyshak a écrit :
Now the default milestone is blank, which is great. Can we also have the
version be blank by default? I think this would help, as discussed
before, so that we know if there is a version specified the user likely
has that version. Currently the defa
On Sat, Mar 21, 2015 at 06:27:17PM -0400, Richard Heck wrote:
> On 03/21/2015 05:59 PM, Scott Kostyshak wrote:
> > On Mon, Mar 16, 2015 at 9:02 PM, Richard Heck wrote:
> > > On 03/16/2015 07:43 PM, Scott Kostyshak wrote:
> > > > 2. version. Currently it defaults to 2.1.3. I propose to have it
> >
On Sun, May 29, 2016 at 10:49:19AM -0400, Richard Heck wrote:
> On 05/29/2016 06:17 AM, Jean-Marc Lasgouttes wrote:
> > I would say that they should be marked as fixed in master, but the
> > fixedinstaging keyword should be kept.
>
> Yes, that seems right.
Makes sense.
Scott
signature.asc
Desc
On 05/29/2016 06:17 AM, Jean-Marc Lasgouttes wrote:
> I would say that they should be marked as fixed in master, but the
> fixedinstaging keyword should be kept.
Yes, that seems right.
Richard
I would say that they should be marked as fixed in master, but the
fixedinstaging keyword should be kept.
JMarc
Le 29 mai 2016 02:14:29 GMT+02:00, Scott Kostyshak a écrit :
>I was going to change trac issues that have the fixedinstaging keyword
>to be fixed in master, but many of these
I was going to change trac issues that have the fixedinstaging keyword
to be fixed in master, but many of these issues are also fixed in
2.2.2-staging. What should these issues be marked as? I'm assuming
fixedinstable is reserved for commits to 2.2.1?
Scott
signature.asc
Description
On 04/18/2016 05:19 PM, Vincent van Ravesteijn wrote:
>
>
> Op 16 apr. 2016 21:50 schreef "Richard Heck" <mailto:rgh...@lyx.org>>:
> >
> >
> > As Scott pointed out, my previous suggestions for how fixes committed to
> > the staging branches
Op 16 apr. 2016 21:50 schreef "Richard Heck" :
>
>
> As Scott pointed out, my previous suggestions for how fixes committed to
> the staging branches should be handled in trac was silly. We can't reuse
> "fixedinmaster" for 2.3-staging. I'm also not
s for how fixes
>>>> committed to
>>>> the staging branches should be handled in trac was silly. We can't
>>>> reuse
>>>> "fixedinmaster" for 2.3-staging. I'm also not sure that we want to
>>>> introduce a new stat
Le 18/04/2016 18:08, Richard Heck a écrit :
On 04/18/2016 06:13 AM, Jean-Marc Lasgouttes wrote:
Le 16/04/2016 21:49, Richard Heck a écrit :
As Scott pointed out, my previous suggestions for how fixes committed to
the staging branches should be handled in trac was silly. We can't
On 04/18/2016 06:13 AM, Jean-Marc Lasgouttes wrote:
> Le 16/04/2016 21:49, Richard Heck a écrit :
>>
>> As Scott pointed out, my previous suggestions for how fixes committed to
>> the staging branches should be handled in trac was silly. We can't reuse
>> "fix
Le 16/04/2016 21:49, Richard Heck a écrit :
As Scott pointed out, my previous suggestions for how fixes committed to
the staging branches should be handled in trac was silly. We can't reuse
"fixedinmaster" for 2.3-staging. I'm also not sure that we want to
introduce a new st
On 04/16/2016 04:19 PM, Guillaume Munch wrote:
> Le 16/04/2016 20:49, Richard Heck a écrit :
>>
>> As Scott pointed out, my previous suggestions for how fixes committed to
>> the staging branches should be handled in trac was silly. We can't reuse
>> "fixedin
Le 16/04/2016 20:49, Richard Heck a écrit :
As Scott pointed out, my previous suggestions for how fixes committed to
the staging branches should be handled in trac was silly. We can't reuse
"fixedinmaster" for 2.3-staging. I'm also not sure that we want to
introduce a new st
As Scott pointed out, my previous suggestions for how fixes committed to
the staging branches should be handled in trac was silly. We can't reuse
"fixedinmaster" for 2.3-staging. I'm also not sure that we want to
introduce a new status "fixedinstaging" for such a
1 - 100 of 614 matches
Mail list logo
