Hi Ceki, I fully understand you.
I was writing another email to the list when i was caught by your reply. So here is another question :) The provided patch is being used by two distinct process of an application logging to the same database. The straightforward approach is to provide separated logging tables for each process, but the database administrators refuses to create two sets of identical tables. The first idea that came up is to add another column to the logging_event table to store some configuration property like the context name so i can use this field to identify which process created the logging event. I can provide this patch too if you think this is useful and of course, makes sense. regards, -- Abraços, Leonardo S Souza 2013/12/12 ceki <[email protected]> > Hi leonardo, > Sending push request us the way to go. My apologies for the delay in > responding to your request. > Best regards, > > > Sent from Samsung Mobile > > > -------- Original message -------- > From: Leonardo Souza > Date:04/12/2013 22:07 (GMT+01:00) > To: [email protected] > Subject: [logback-dev] pull request > > > Hi, > > I have created this pull request 4 months ago. > > https://github.com/qos-ch/logback/pull/141 > > This is my first pull request on github. > Did I make something wrong or is just a matter of time to see this patch > merged into the master branch? > > > -- > regards > Leonardo S Souza > > > _______________________________________________ > logback-dev mailing list > [email protected] > http://mailman.qos.ch/mailman/listinfo/logback-dev >
_______________________________________________ logback-dev mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-dev
